ci: pin supabase/sdk validate-capabilities workflow to v1.0.0 - #1572
Merged
Conversation
supabase/sdk cut its first tagged release, v1.0.0. Pin the reusable validate-capabilities workflow ref to that release's commit SHA with a version comment instead of a floating @main ref. Dependabot's github-actions ecosystem (already configured here) picks up the version comment and will open PRs to bump this as supabase/sdk cuts new releases.
Contributor
|
The following capabilities are marked
The following capabilities are marked
These may have been renamed, removed, or never registered. Please update the capability matrix. |
mandarini
approved these changes
Aug 12, 2026
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
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.
Summary
validate-capabilities.yml'suses:ref to that release's commit SHA with a# v1.0.0comment, instead of a floating@mainref. (This repo doesn't have a sync-compliance.yml, so that's the only file to update.)github-actionsecosystem (already configured in.github/dependabot.yml) recognizes the version comment and will open PRs here as supabase/sdk cuts new releases, so this stays current automatically.Test plan
Validate SDK Complianceworkflow still runs successfully against the pinned ref