docs(release): notes for v2.109.1#5817
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: f564fcd561
ℹ️ 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".
|
|
||
| - **Error messages guide flag placement** — the CLI suggests correct subcommand placement when flags are misplaced. (#5751) | ||
| - **Shell completion customization** — `--no-descriptions` flag suppresses descriptions in shell completions. (#5771) | ||
| - **Non-TypeScript type generation** — `gen types` now works for JavaScript and other languages. (#5622) |
There was a problem hiding this comment.
The gen types command still only accepts typescript, go, swift, or python (apps/cli/src/legacy/commands/gen/types/types.command.ts:9), and #5622 enabled project-ref generation for Go/Swift/Python rather than a JavaScript output. Publishing this as "works for JavaScript" points users at an unsupported --lang=javascript; please name the supported languages instead.
Useful? React with 👍 / 👎.
|
|
||
| ### Bug fixes | ||
|
|
||
| - **`db pull` no longer hangs in non-interactive mode** — fixed hang when using `db pull` without interactive prompts. (#5725) |
There was a problem hiding this comment.
The #5725 prompt fix also changed config push and logout: config push now resolves SUPABASE_YES from the project env before prompting and uses the shared Go-compatible prompt helper, and logout now uses the same helper for piped/non-TTY stdin (apps/cli/src/legacy/commands/config/push/push.handler.ts:94-103, apps/cli/src/legacy/commands/logout/logout.handler.ts:24-36). Limiting the note to db pull leaves CI users with hanging config push cost prompts or scripted logout unaware their workflows are fixed.
Useful? React with 👍 / 👎.
|
|
||
| --- | ||
|
|
||
| Plus internal improvements including service version alignment and experimental feature gating enhancements, plus dependency and Docker image updates. |
There was a problem hiding this comment.
The tail calls this internal, but #5766 adds a runtime gate that makes postgres-config, ssl-enforcement, and network-bans leaf commands fail without --experimental / SUPABASE_EXPERIMENTAL (apps/cli/src/legacy/commands/postgres-config/get/get.command.ts:33-40, apps/cli/src/legacy/commands/ssl-enforcement/get/get.command.ts:33-40, and similarly network-bans). That changes the error users see and the required invocation for those commands, so it should be called out as a user-visible gotcha/fix rather than buried in the internal-improvements sentence.
Useful? React with 👍 / 👎.
1 participant
Proposed user-facing release notes for
v2.109.1, generated byapps/cli/scripts/propose-release-notes.tsagainsttools/release/release-notes-prompt.md.How to update the notes
Edit
release-notes/v2.109.1.mddirectly on this branch — use the GitHub web editor or push commits torelease-notes/v2.109.1— 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.109.1with the contents ofrelease-notes/v2.109.1.md.release-notes/v2.109.1branch.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.109.1stays in place.Re-generation
After this PR is closed, rerun the Propose release notes workflow from the Actions tab against
v2.109.1to get a fresh proposal.