chore: release main - #114
Merged
Merged
Conversation
This was referenced Aug 28, 2026
spydon
added a commit
that referenced
this pull request
Aug 28, 2026
## Summary Stops versioning the repository root with release-please and versions packages individually instead. The root `vX.Y.Z` release line ends at `v1.5.0`; from here on, `packages/capability-matrix` and `packages/postgrest-typegen` each have their own component, tags, and changelog, and the compliance logic moves into the package that versions it. ## What changed - **`release-please-config.json`**: removes the root `"."` component. Adds `packages/capability-matrix` as a `node` component (component name `capability-matrix`, tags `capability-matrix-vX.Y.Z`). `packages/postgrest-typegen` keeps the setup from #111. The symbol extractors (`dart-symbol-extractor`, `go-symbol-extractor`) are intentionally not release-managed. - **`.release-please-manifest.json`**: replaces the `"."` entry with `packages/capability-matrix` at `1.5.0`. capability-matrix continues the root release line rather than restarting at `0.x`, so consumer pins migrate from `v1.5.0` to `capability-matrix-v1.6.0` without a version regression. `packages/capability-matrix/package.json` is aligned to `1.5.0` for the same reason. - **Composite actions**: the four `sdk-compliance-*` actions move from `.github/actions/` to `packages/capability-matrix/actions/` (pure renames), and the five reusable workflow wrappers update their references. The wrappers resolve the actions through the `_sdk-spec` checkout pinned at `job.workflow_sha`, so existing consumer pins keep resolving the old layout at their own SHA; nothing breaks for repos still on `v1.x`. - **`CLAUDE.md`**: documents the new layout and release flow. ## First-release version pins Release-please bootstraps a tagless component by scanning the entire history, and it honors old unscoped `chore: release X.Y.Z` commits as implicit Release-As overrides that beat the manifest version. That is why #114 currently proposes 1.3.0 for postgrest-typegen: it picked up `chore: release 1.3.0` (#97), which never touched the package. Both components therefore carry a temporary pin: - `packages/postgrest-typegen`: `release-as: 0.1.0`, matching its `package.json`. #114 regenerates to 0.1.0 once this merges. - `packages/capability-matrix`: `release-as: 1.6.0`, continuing the root line. `release-as` is sticky: each pin must be removed in a follow-up right after that component's first release merges. ## How consumers version the reusable workflows after this GitHub requires `workflow_call` workflows to live in `.github/workflows/`, so the wrappers cannot move. With the compliance logic inside `packages/capability-matrix`, any meaningful change to workflow behavior lands in the package and cuts a `capability-matrix-vX.Y.Z` tag. SDK repos pin that tag directly: ```yaml uses: supabase/sdk/.github/workflows/validate-sdk-compliance-dart.yml@capability-matrix-v1.6.0 ``` A tag is just a ref, and `job.workflow_sha` resolves tooling, actions, and spec from that same commit, so the whole bundle travels with the capability-matrix version. Dependabot handles the prefixed tag format: it derives the prefix from the current pin and only offers updates within the same tag family, so `capability-matrix-v*` pins stay on their line. The initial repin from `v1.x` is a one-time manual change per consumer repo. The wrappers become thin shims (checkout plus action reference). A wrapper-only change does not bump the capability-matrix component by itself; if one ever needs to ship alone, force a release with a `Release-As: x.y.z` commit footer. ## Merge order 1. This PR. 2. The regenerated #114 (postgrest-typegen 0.1.0). Before its publish job can succeed, `@supabase/postgrest-typegen` needs a one-time manual bootstrap on npm: stub-publish a version below 0.1.0, then configure the trusted publisher for `release.yml`. 3. Follow-ups: remove each `release-as` pin after that component's first release, then bump consumer repo pins to `capability-matrix-v1.6.0`.
supabase-releaser
Bot
force-pushed
the
release-please--branches--main
branch
from
August 28, 2026 14:16
4a8f1fb to
55096f4
Compare
spydon
approved these changes
Aug 28, 2026
Contributor
Author
|
🤖 Created releases: 🌻 |
supabase-releaser
Bot
added
autorelease: tagged
and removed
autorelease: pending
labels
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
🤖 I have created a release beep boop
capability-matrix: 1.6.0
1.6.0 (2026-08-28)
Features
Bug Fixes
Miscellaneous Chores
postgrest-typegen: 0.1.0
0.1.0 (2026-08-28)
Features
Miscellaneous Chores
This PR was generated with Release Please. See documentation.