supabase
/
mcp
96%
|
Repo Added
|
Build
15
Last
|
Files
32
|
Badge
Embed ▾
README BADGES
|
LAST BUILD ON BRANCH
main
branch: SELECT
CHANGE BRANCH
x
-
No branch selected
-
ci/force-publish-workflow
-
fix/repo-transfer-urls
-
main
-
release-please--branches--main
CHANGE BRANCH
x
-
No branch selected
- ci/force-publish-workflow
- fix/repo-transfer-urls
- main
- release-please--branches--main
coverage: 96.243%. Remained the same
push
github
web-flowci: add force_publish input to release workflow (#303) Adds a `force_publish` boolean input to the Release workflow's manual dispatch, adapted from the [pattern in Greg's reposh](https://github.com/supabase-community/reposh/blob/faad5c895/.github/workflows/release.yml#L8-L11). Useful when the release workflow fails partway through, [example instance](https://supabase.slack.com/archives/C02AK9166FR/p1780935267920019?thread_ts=1780513141.174739&cid=C02AK9166FR). When checked, bypasses release-please gating and runs build + all publish steps against current `package.json` versions. Only packages missing from npm actually publish. Also checks MCP registry for existing version before publication to keep the workflow idempotent. Regenerated mgmt-api types for required check. Closes AI-828
313 of 347 branches covered (90.2%)
Branch coverage included in aggregate %.
2735 of 2820 relevant lines covered (96.99%)
41.15 hits per line
Relevant lines Covered
2820
RELEVANT LINES
2735
COVERED LINES
41.15
HITS PER LINE
Source Files on main
Recent builds
 |
Badge your Repo: mcpWe detected this repo isn’t badged! Grab the embed code to the right, add it to your repo to show off your code coverage, and when the badge is live hit the refresh button to remove this message. |
|
Embed ▾
Refresh
README BADGES
|