Repository navigation
chore: refresh platform-openapi.json - #121
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Refreshes `specs/platform-openapi.json` from firstlanding `origin/main` (044810d106) via `mix api_dsl.gen.docs.openapi` (412 routes, 511 schemas, 5 channels). Same output as the `publish-openapi-spec` workflow in firstlanding; run locally so it stays on this PR flow.
Why
Publish the current Platform API as a new `@archastro/sdk` release (this PR, then regenerate archastro-js/archastro-python, then release).
Diff summary
Scope / risk / testing
Spec-only, no code. Low risk. CI runs generator lint + tests; downstream SDK PRs run contract tests against this spec.
🤖 Generated with Claude Code