docs(release): notes for v2.105.0#5477
Closed
supabase-cli-releaser[bot] wants to merge 1 commit into
Closed
Conversation
jgoux
approved these changes
Jun 4, 2026
Contributor
Author
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
1 participant
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.
Proposed user-facing release notes for
v2.105.0, generated byapps/cli/scripts/propose-release-notes.tsagainsttools/release/release-notes-prompt.md.How to update the notes
Edit
release-notes/v2.105.0.mddirectly on this branch — use the GitHub web editor or push commits torelease-notes/v2.105.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.105.0with the contents ofrelease-notes/v2.105.0.md.release-notes/v2.105.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.105.0stays in place.Re-generation
After this PR is closed, rerun the Propose release notes workflow from the Actions tab against
v2.105.0to get a fresh proposal.