docs(release): notes for v2.113.0 - #6124
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 39010daed4
ℹ️ 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".
| This release improves error reporting and continues the TypeScript migration. The CLI now properly surfaces `serve` staging errors and handles timestamps with timezone offsets. | ||
|
|
||
| ### Bug fixes | ||
| - `supabase serve` now displays staging errors instead of suppressing them (#6113) |
There was a problem hiding this comment.
This publishes the fix as supabase serve, but the legacy command tree registers serve only underneath functions (legacyFunctionsCommand includes legacyFunctionsServeCommand, and that command is Command.make("serve")), and the generated reference documents the usage as supabase functions serve. As written, users may look for a nonexistent top-level command; please name this as supabase functions serve in the release notes.
Useful? React with 👍 / 👎.
1 participant
Proposed user-facing release notes for
v2.113.0, generated byapps/cli/scripts/propose-release-notes.tsagainsttools/release/release-notes-prompt.md.How to update the notes
Edit
release-notes/v2.113.0.mddirectly on this branch — use the GitHub web editor or push commits torelease-notes/v2.113.0— before approving. The applied notes will reflect the file at the approved commit.How to publish
Approve this PR as a
supabase/cliteam member. The.github/workflows/apply-release-notes.ymlworkflow will then:v2.113.0with the contents ofrelease-notes/v2.113.0.md.release-notes/v2.113.0branch.This PR is not merged — the
do not mergelabel is a reminder. It targetsdevelopso that even an accidental merge never rewritesmain. Nothing is meant to land on any branch.Approvals from anyone outside the
supabase/cliteam are ignored; the workflow will post a comment explaining that and leave the release untouched.How to abandon
Close the PR without approving. The auto-generated semantic-release body for
v2.113.0stays in place.Re-generation
After this PR is closed, rerun the Propose release notes workflow from the Actions tab against
v2.113.0to get a fresh proposal.