• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

supabase / supabase-py / 41848247294
98%

Build:
DEFAULT BRANCH: main
Ran 04 Nov 2026 02:30PM UTC
Jobs 36
Files 99
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

04 Nov 2026 02:30PM UTC coverage: 94.502%. Remained the same
41848247294

push

github

web-flow
ci: fix release-please prerelease version bumps (#1973)

## 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.

8456 of 8948 relevant lines covered (94.5%)

5.75 hits per line

Jobs
ID Job ID Ran Files Coverage
1 storage-py3.14-highest - 41848247294.1 04 Nov 2026 02:31PM UTC 22
93.21
GitHub Action Run
2 postgrest-py3.14-highest - 41848247294.2 04 Nov 2026 02:32PM UTC 24
97.53
GitHub Action Run
3 storage-py3.11-lowest-direct - 41848247294.3 04 Nov 2026 02:32PM UTC 22
93.24
GitHub Action Run
4 auth-py3.11-lowest-direct - 41848247294.4 04 Nov 2026 02:31PM UTC 34
91.52
GitHub Action Run
5 supabase-py3.11-highest - 41848247294.5 04 Nov 2026 02:30PM UTC 19
92.79
GitHub Action Run
6 auth-py3.12-highest - 41848247294.6 04 Nov 2026 02:31PM UTC 34
91.52
GitHub Action Run
7 supabase-py3.13-highest - 41848247294.7 04 Nov 2026 02:30PM UTC 19
92.79
GitHub Action Run
8 functions-py3.13-highest - 41848247294.8 04 Nov 2026 02:30PM UTC 14
97.4
GitHub Action Run
9 auth-py3.14-highest - 41848247294.9 04 Nov 2026 02:31PM UTC 34
91.49
GitHub Action Run
10 postgrest-py3.11-lowest-direct - 41848247294.10 04 Nov 2026 02:32PM UTC 24
97.54
GitHub Action Run
11 postgrest-py3.15-highest - 41848247294.11 04 Nov 2026 02:32PM UTC 24
97.53
GitHub Action Run
12 functions-py3.11-lowest-direct - 41848247294.12 04 Nov 2026 02:30PM UTC 14
97.4
GitHub Action Run
13 supabase-py3.15-highest - 41848247294.13 04 Nov 2026 02:32PM UTC 19
92.76
GitHub Action Run
14 realtime-py3.11-lowest-direct - 41848247294.14 04 Nov 2026 02:32PM UTC 8
96.37
GitHub Action Run
15 functions-py3.11-highest - 41848247294.15 04 Nov 2026 02:30PM UTC 14
97.4
GitHub Action Run
16 supabase-py3.14-highest - 41848247294.16 04 Nov 2026 02:30PM UTC 19
92.76
GitHub Action Run
17 supabase-py3.12-highest - 41848247294.17 04 Nov 2026 02:30PM UTC 19
92.79
GitHub Action Run
18 realtime-py3.15-highest - 41848247294.18 04 Nov 2026 02:32PM UTC 8
95.96
GitHub Action Run
19 supabase-py3.11-lowest-direct - 41848247294.19 04 Nov 2026 02:30PM UTC 19
92.79
GitHub Action Run
20 auth-py3.11-highest - 41848247294.20 04 Nov 2026 02:31PM UTC 34
91.52
GitHub Action Run
21 auth-py3.13-highest - 41848247294.21 04 Nov 2026 02:31PM UTC 34
91.52
GitHub Action Run
22 storage-py3.12-highest - 41848247294.22 04 Nov 2026 02:32PM UTC 22
93.24
GitHub Action Run
23 realtime-py3.11-highest - 41848247294.23 04 Nov 2026 02:32PM UTC 8
96.51
GitHub Action Run
24 storage-py3.11-highest - 41848247294.24 04 Nov 2026 02:32PM UTC 22
93.24
GitHub Action Run
25 realtime-py3.13-highest - 41848247294.25 04 Nov 2026 02:32PM UTC 8
96.37
GitHub Action Run
26 realtime-py3.12-highest - 41848247294.26 04 Nov 2026 02:32PM UTC 8
96.37
GitHub Action Run
27 functions-py3.14-highest - 41848247294.27 04 Nov 2026 02:30PM UTC 14
97.4
GitHub Action Run
28 storage-py3.13-highest - 41848247294.28 04 Nov 2026 02:32PM UTC 22
93.24
GitHub Action Run
29 functions-py3.12-highest - 41848247294.29 04 Nov 2026 02:30PM UTC 14
97.4
GitHub Action Run
30 auth-py3.15-highest - 41848247294.30 04 Nov 2026 02:31PM UTC 34
91.49
GitHub Action Run
31 postgrest-py3.11-highest - 41848247294.31 04 Nov 2026 02:32PM UTC 24
97.54
GitHub Action Run
32 realtime-py3.14-highest - 41848247294.32 04 Nov 2026 02:32PM UTC 8
95.96
GitHub Action Run
33 functions-py3.15-highest - 41848247294.33 04 Nov 2026 02:31PM UTC 14
97.4
GitHub Action Run
34 postgrest-py3.12-highest - 41848247294.34 04 Nov 2026 02:32PM UTC 24
97.54
GitHub Action Run
35 storage-py3.15-highest - 41848247294.35 04 Nov 2026 02:32PM UTC 22
93.21
GitHub Action Run
36 postgrest-py3.13-highest - 41848247294.36 04 Nov 2026 02:32PM UTC 24
97.54
GitHub Action Run
Source Files on build 41848247294
  • Tree
  • List 99
  • Changed 1
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #41848247294
  • 9ec8e525 on github
  • Prev Build on main (#41846138912)
  • Next Build on main (#41853017234)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc