You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ci: fix release-please prerelease version bumps - #1973
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.
No actionable comments were generated in the recent review.
Summary
Summary by CodeRabbit
Chores
Updated the 3.0.0 alpha version identifiers across the Python packages to use consistent prerelease formatting.
Aligned package and dependency version constraints with the updated format, including optional and test dependencies.
Package versions and dependency pins change from 3.0.0a1 to 3.0.0-a1. The corresponding package __version__ values use the updated spelling. Release-please configuration now lists the affected pyproject.toml files as generic extra files and adds src/utils/pyproject.toml.
Possibly related PRs
supabase/supabase-py#1370: Adds the src/utils/pyproject.toml package file that this change adds to release-please configuration.
Change: Bug fix
Merge Risk: Minimal · up to e2e2f
The prerelease version spelling and release configuration are aligned. No merge-blocking issue is identified; merge after normal checks pass.
- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: CHILL
Plan: Advanced
Run ID: 339060ae-cff0-4d79-b3e3-ae51ad37518e
Commits
Reviewing files that changed from the base of the PR and between 8b8fb5e and e2e2f2b.
Files selected for processing: 14
release-please-config.json
src/auth/pyproject.toml
src/auth/src/supabase_auth/version.py
src/functions/pyproject.toml
src/functions/src/supabase_functions/version.py
src/postgrest/pyproject.toml
src/postgrest/src/postgrest/version.py
src/realtime/pyproject.toml
src/realtime/src/realtime/version.py
src/storage/pyproject.toml
src/storage/src/storage3/version.py
src/supabase/pyproject.toml
src/supabase/src/supabase/version.py
src/utils/pyproject.toml
Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 0 remain after this review.
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
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.
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'sgenericupdater only recognizes semver prereleases (3.0.0-a1), so it matched3.0.0, replaced it with3.0.0-a2, and left the trailinga1behind. Thetomlupdaters replaced onlyproject.version, so thesupabase_utilspins in those files were never bumped.src/utilswas not inextra-filesat all.Changes
3.0.0-a1). This is valid PEP 440 and normalizes to3.0.0a1, so built wheels anduv.lockare unchanged.genericupdater for everypyproject.toml, so the dependency pins are bumped together with the package version.src/utils/pyproject.tomltoextra-files.supabase_utils[all]dev pins infunctionsandpostgrestso they are bumped too.Verification
uv lock --checkpasses anduv.lockis unchanged.3.0.0-a1to3.0.0-a2on every marked line).uv lockresolves, every package builds, and the installed metadata reports3.0.0a2.Once merged, release-please regenerates #1959.
__version__will now read3.0.0-a2at runtime, so the client info headers report the hyphenated form. Package metadata stays normalized.