Repository navigation
chore(main): release 3.0.0-a2 - #1959
Open
supabase-py-releaser[bot] wants to merge 1 commit into
Open
supabase-py-releaser[bot] wants to merge 1 commit into
supabase-py-releaser[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
supabase-py-releaser
Bot
force-pushed
the
release-please--branches--main
branch
2 times, most recently
from
November 4, 2026 14:15
2eb9bee to
2302b72
Compare
spydon
added a commit
that referenced
this pull request
Nov 4, 2026
## Summary The release PR (#1959) fails every CI job because release-please writes invalid versions such as `3.0.0-a2a1`. The marked files used the PEP 440 form `3.0.0a1`. Release-please's `generic` updater only recognizes semver prereleases (`3.0.0-a1`), so it matched `3.0.0`, replaced it with `3.0.0-a2`, and left the trailing `a1` behind. The `toml` updaters replaced only `project.version`, so the `supabase_utils` pins in those files were never bumped. `src/utils` was not in `extra-files` at all. ## Changes - Write every release-please managed version in the hyphenated form (`3.0.0-a1`). This is valid PEP 440 and normalizes to `3.0.0a1`, so built wheels and `uv.lock` are unchanged. - Use the `generic` updater for every `pyproject.toml`, so the dependency pins are bumped together with the package version. - Add `src/utils/pyproject.toml` to `extra-files`. - Mark the `supabase_utils[all]` dev pins in `functions` and `postgrest` so they are bumped too. ## Verification - `uv lock --check` passes and `uv.lock` is unchanged. - Simulated the next bump (`3.0.0-a1` to `3.0.0-a2` on every marked line). `uv lock` resolves, every package builds, and the installed metadata reports `3.0.0a2`. Once merged, release-please regenerates #1959. `__version__` will now read `3.0.0-a2` at runtime, so the client info headers report the hyphenated form. Package metadata stays normalized.
supabase-py-releaser
Bot
force-pushed
the
release-please--branches--main
branch
24 times, most recently
from
November 10, 2026 16:22
cad445f to
495c561
Compare
supabase-py-releaser
Bot
force-pushed
the
release-please--branches--main
branch
10 times, most recently
from
November 11, 2026 14:29
a5164c2 to
fcfad81
Compare
supabase-py-releaser
Bot
force-pushed
the
release-please--branches--main
branch
from
November 11, 2026 15:18
fcfad81 to
308be5a
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-a2 (2026-11-11)
⚠ BREAKING CHANGES
Features
Bug Fixes
Documentation
Miscellaneous Chores
Code Refactoring
This PR was generated with Release Please. See documentation.