Uh oh!
There was an error while loading. Please reload this page.
ci(cli): publish ts docs reference (CLI-2171) - #6253
Conversation
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase/cli/supabase@afa50414ccde59ef506f08155421a4d306ecf651Preview package for commit |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:573b364862
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
…i-reference # Conflicts: # apps/cli/package.json # pnpm-lock.yaml
…i-reference # Conflicts: # apps/cli/package.json # pnpm-lock.yaml
Uh oh!
There was an error while loading. Please reload this page.
gofmt -l flagged pkg/config/db.go and pkg/function/deploy_test.go (pre-existing whitespace drift from #6253); fixed so the Go CI format check stays green on branches touching apps/cli-go. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BQAoY9JF4uiZRvKVkSd9Wy
TL;DR
fixes the CLI docs reference being frozen at v2.98.2
which was caused by the monorepo merge deleting the Go bumpdoc docs job from the release workflow,
and is now fixed by a stable-only docs job that regenerates the spec from the TS command tree and delivers it to supabase/supabase the same way bumpdoc did...
whats introduced?
docsjob in release.yml: stable releases only, runs after publish, non-blocking for the release, and mints the same scoped App token...scripts/publish-docs-spec.ts: reads the generated spec on stdin, validates it(clispec 001, version match, command count) before any network action, formats it with a pinned prettier to match the published file's style, then updates the
cli/ref-docbranch in supabase/supabase and opens a PR when none is open..cli/ref-docalready exists the new spec lands as a commit on top, so fixes pushed onto an open bot PR survive later releaseshow?
stable release now runs
generate-docs-spec.ts "$VERSION" | publish-docs-spec.ts --version "$VERSION"which lands a validated, formatted spec as a commit on
cli/ref-docand opens thefamiliar
chore: update cli reference docPR for the docs team to mergea stable dry run exercises the same pipe with
--dry-run, which also verifies the App token mint without pushing anything up..Note
will follow up on
supabase/supabasewith a spec-to-sidebar coverage guard,so a new command missing a
common-cli-sections.jsonentry fails the bot PR instead of silently publishing no page...ref: