Repository navigation
chore(main): release 3.0.0-alpha.2 - #1834
Open
supabase-releaser[bot] wants to merge 1 commit into
Open
supabase-releaser[bot] wants to merge 1 commit into
supabase-releaser[bot] wants to merge 1 commit into
Conversation
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Coverage Report for CI Build 44408592637Coverage decreased (-0.03%) to 96.193%Details
Uncovered ChangesNo uncovered changes found. Coverage Regressions5 previously-covered lines in 1 file lost coverage.
Coverage Stats
💛 - Coveralls |
supabase-releaser
Bot
force-pushed
the
release-please--branches--main
branch
19 times, most recently
from
November 18, 2026 19:20
bd67721 to
08b0e0f
Compare
supabase-releaser
Bot
force-pushed
the
release-please--branches--main
branch
from
November 18, 2026 22:08
08b0e0f to
b9e17ef
Compare
This branch has not been deployed
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
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.
🤖 I have created a release beep boop
3.0.0-alpha.2 (2026-11-18)
⚠ BREAKING CHANGES
headersin that case.Accept: application/vnd.pgrst.object+json, so PostgREST no longer rolls back a write that matches more than one row. The rows are written, then the call throws PGRST116. Use single() where the rollback matters. The typed maybeSingle() throws a .server error instead of .decoding.Features
Bug Fixes
Code Refactoring
This PR was generated with Release Please. See documentation.