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

supabase / supabase-flutter / 41422289225
94%

Build:
DEFAULT BRANCH: main
Ran 02 Nov 2026 09:39AM UTC
Jobs 12
Files 193
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

02 Nov 2026 09:38AM UTC coverage: 94.13%. Remained the same
41422289225

push

github

web-flow
docs(supabase_typegen): say when to regenerate the schema in the package skills (#2115)

## Summary

The package skills told agents to regenerate
`lib/supabase_schema.g.dart` only "after every database migration". That
misses several cases where the generated file goes stale. The generate,
idioms and migrate-v3 skills now say to regenerate:

- after any change to the database schema, including changes made in the
dashboard or with SQL against a hosted project, and migrations pulled
from another branch,
- after upgrading `supabase_typegen` or the Supabase CLI.

The generate and idioms skills also say that with `--local`, new
migrations must be applied to the stack first (`supabase migration up`
or `supabase db reset`), since the command reads the running database
and otherwise produces the old schema without an error. The idioms skill
now mentions `--linked` and `--project-id` next to `--local`.

The generated `skills/` folders were updated with `melos run
sync-skills`.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->

## Summary by CodeRabbit

* **Documentation**
* Expanded schema-generation guidance to cover changes from migrations,
dashboards, hosted SQL, and other branches, plus upgrades to the
Supabase CLI or type-generation tools.
* Clarified that local migrations must be applied before generating
types locally, and that generation should target the database containing
the schema change. Hosted schemas can be used with a linked project or
project reference.
* Warned that editing an already-applied migration does not reapply it
automatically, and requires user approval before a local reset that
could discard data.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

12539 of 13321 relevant lines covered (94.13%)

6.64 hits per line

Jobs
ID Job ID Ran Files Coverage
3 supabase_functions - 41422289225.3 02 Nov 2026 09:39AM UTC 4
94.01
GitHub Action Run
4 supabase_typegen - 41422289225.4 02 Nov 2026 09:41AM UTC 6
94.44
GitHub Action Run
5 supabase_test - 41422289225.5 02 Nov 2026 09:39AM UTC 9
93.55
GitHub Action Run
6 supabase_auth - 41422289225.6 02 Nov 2026 09:42AM UTC 34
94.21
GitHub Action Run
7 postgrest - 41422289225.7 02 Nov 2026 09:42AM UTC 30
92.86
GitHub Action Run
8 supabase_storage - 41422289225.8 02 Nov 2026 09:41AM UTC 13
95.96
GitHub Action Run
9 supabase - 41422289225.9 02 Nov 2026 09:42AM UTC 21
94.52
GitHub Action Run
10 iceberg - 41422289225.10 02 Nov 2026 09:39AM UTC 7
99.72
GitHub Action Run
11 supabase_realtime - 41422289225.11 02 Nov 2026 09:42AM UTC 14
92.0
GitHub Action Run
12 supabase_flutter - 41422289225.12 02 Nov 2026 09:40AM UTC 16
89.03
GitHub Action Run
3 yet_another_json_isolate - 40346664947.3 26 Oct 2026 03:11PM UTC 2
98.65
GitHub Action Run
2 supabase_common - 40911627463.2 29 Oct 2026 04:28PM UTC 37
94.39
GitHub Action Run
Source Files on build 41422289225
  • Tree
  • List 193
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #41422289225
  • 8bf5f102 on github
  • Prev Build on main (#41417592519)
  • Next Build on main (#41427870403)
  • 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