fix(ci): unquoted colon made compliance action manifests invalid YAML - #109
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
QuintinWillison
approved these changes
Aug 28, 2026
spydon
pushed a commit
that referenced
this pull request
Aug 28, 2026
🤖 I have created a release *beep* *boop* --- ## [1.5.0](v1.4.0...v1.5.0) (2026-08-28) ### Features * **postgrest-typegen:** add PostgREST introspection engine (+ transitional TS/Go/Python/Swift generators) ([#94](#94)) ([3d63578](3d63578)) ### Bug Fixes * **ci:** unquoted colon made compliance action manifests invalid YAML ([#109](#109)) ([fd53fdb](fd53fdb)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: supabase-releaser[bot] <223506987+supabase-releaser[bot]@users.noreply.github.com>
This was referenced Aug 28, 2026
Merged
spydon
added a commit
to supabase/supabase-flutter
that referenced
this pull request
Aug 28, 2026
Bumps the pinned supabase/sdk reusable workflows from v1.3.0 to v1.5.0 (`75cf587c486f80c2d2afe57ec909ee2520c098b9`). v1.4.0 (supabase/sdk#107) resolves the compliance tooling, composite actions, and capability spec from the single supabase/sdk commit this pin points at (`job.workflow_sha`), instead of referencing the actions remotely at `@main` while the workflow itself is SHA-pinned. This removes the tooling/spec version skew that broke supabase-go CI after the `packages/` restructure in supabase/sdk, and makes the SHA pin here fully effective: the action code executed can no longer drift from the pinned workflow. v1.5.0 additionally includes supabase/sdk#109, which fixes an unquoted colon that made the compliance composite action manifests invalid YAML, so this is the first release where the workflow-SHA resolution from #107 actually runs. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated SDK compliance checks to the latest workflow version. * Applied the update across compliance synchronization and capability validation workflows. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
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
2 participants
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.
What
Rewords the transitional
sdk-refinput descriptions insdk-compliance-validateandsdk-compliance-check-setupfromTransitional: only ...toTransitional, only ....Why
The unquoted
Transitional: only ...scalar introduced in #107 contains a colon-space, which YAML parses as a nested mapping, making both action manifests invalid:This currently fails every consumer compliance run: v1.4.0 callers load the actions from the pinned checkout, and pre-v1.4.0 callers load them remotely at
@main, so both paths hit the broken manifests. Example: https://github.com/supabase/supabase-flutter/actions/runs/33163722404/job/98824054540actionlint did not catch it because it lints workflow files only, not composite action manifests; both files now pass a YAML parse check.
Follow-up
Cut v1.4.1 so the pinned consumers can bump;
@mainconsumers recover on merge.