docs(release): notes for v2.110.0

[supabase-cli-releaser]

Proposed user-facing release notes for v2.110.0, generated by apps/cli/scripts/propose-release-notes.ts against tools/release/release-notes-prompt.md.

How to update the notes

Edit release-notes/v2.110.0.md directly on this branch — use the GitHub web editor or push commits to release-notes/v2.110.0 — before approving. The applied notes will reflect the file at the approved commit.

How to publish

Approve this PR as a supabase/cli team member. The .github/workflows/apply-release-notes.yml workflow will then:

1. Overwrite the GitHub Release body for v2.110.0 with the contents of release-notes/v2.110.0.md.
2. Comment the release URL on this PR.
3. Close this PR and delete the release-notes/v2.110.0 branch.

This PR is not merged — the do not merge label is a reminder. It targets develop so that even an accidental merge never rewrites main. Nothing is meant to land on any branch.

Approvals from anyone outside the supabase/cli team 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.110.0 stays in place.

Re-generation

After this PR is closed, rerun the Propose release notes workflow from the Actions tab against v2.110.0 to get a fresh proposal.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:86064c59ac

ℹ️ 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".

[supabase-cli-releaser]

Applied to v2.110.0 after approval by @Coly010.