supabase / supabase-flutter / 32709892111
89%

DEFAULT BRANCH: main
Ran
Jobs 10
Files 120
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
coverage: 88.576%. Remained the same
32709892111

push

github

web-flow 
chore: publish packages as 3.0.0-dev.1 (#1754)

Pre-release versioning run for the v3 train. Every published SDK package
lands on `3.0.0-dev.1` so the whole set can go to pub.dev as a coherent
prerelease.

## Versions

| Package | Before | After |
| --- | --- | --- |
| `supabase_common` | 0.1.2 | 3.0.0-dev.1 |
| `postgrest` | 2.9.1 | 3.0.0-dev.1 |
| `supabase_auth` | 3.0.0-dev.1 | 3.0.0-dev.1 |
| `supabase_functions` | 3.0.0-dev.1 | 3.0.0-dev.1 |
| `supabase_realtime` | 3.0.0-dev.1 | 3.0.0-dev.1 |
| `supabase_storage` | 3.0.0-dev.1 | 3.0.0-dev.1 |
| `supabase` | 2.16.0 | 3.0.0-dev.1 |
| `supabase_flutter` | 2.17.1 | 3.0.0-dev.1 |

`supabase_auth`, `supabase_functions`, `supabase_realtime` and
`supabase_storage` already carried `3.0.0-dev.1` in their pubspec, but
that number was hand-set during the package renames and never published,
so no matching changelog section existed. This run generates it and
leaves the version where it is.

## iceberg

`iceberg` stays on `0.1.0`. It has never been published, so its
accumulated changes are folded into the existing `## 0.1.0` changelog
section instead of opening a new one. `supabase_storage` keeps its
`iceberg: 0.1.0` constraint.

## Not versioned

- `yet_another_json_isolate` stays on 2.1.1
- `supabase_testing` stays on 0.1.0
- `supabase_lints` and `supabase_typegen` stay on 0.1.1, they version on
their own tooling track

Their pubspec versions and changelogs are untouched, as are the
constraints pointing at them (`yet_another_json_isolate: 2.1.1`,
`supabase_lints: ^0.1.1`).

## What changed

- Package `pubspec.yaml` versions plus the intra-workspace dependency
constraints between them
- `lib/src/version.dart` for `postgrest`, `supabase` and
`supabase_flutter`, regenerated by the `update-version` melos hook
- Per-package `CHANGELOG.md` and the workspace `CHANGELOG.md`
- `supabase_flutter: ^3.0.0-dev.1` and `supabase: ^3.0.0-dev.1` in the
example apps

## How it was generated

`melos version` with an explicit `... (continued)

5978 of 6749 relevant lines covered (88.58%)

4.44 hits per line

Jobs
ID Job ID Ran Files Coverage
8 supabase_common - 32709892111.8 21
86.96
 GitHub Action Run
9 supabase_functions - 32709892111.9 4
97.83
 GitHub Action Run
10 iceberg - 32709892111.10 6
68.52
 GitHub Action Run
10 postgrest - 32488229193.10 11
84.5
 GitHub Action Run
3 supabase_storage - 32488229193.3 9
97.31
 GitHub Action Run
9 supabase_auth - 32488229193.9 30
90.67
 GitHub Action Run
2 yet_another_json_isolate - 32488229193.2 1
98.44
 GitHub Action Run
4 supabase_flutter - 32488229193.4 11
82.11
 GitHub Action Run
8 supabase_realtime - 32488229193.8 13
90.15
 GitHub Action Run
6 supabase - 32488229193.6 14
93.58
 GitHub Action Run
Source Files on build 32709892111