ci(supabase): validate local stack in CI#16
Merged
Conversation
## Summary - Add a GitHub Actions job that starts the Supabase Docker stack and validates local migrations. - Extend the backend verifier so CI can fail on non-pass JSON status rows and archive evidence. - Sync release runbooks and source guards with the CI-owned Docker validation path. ## Changes Made ### GitHub Actions - Added the supabase-local-validation job to start Supabase, reset local migrations, run backend verification, upload evidence, and stop containers. ### Verification Script - Added -RequireAllPass and -OutFile to scripts/verify_supabase_backend.ps1. - Kept verification SQL validation read-only and repository-contained evidence output guarded. ### Docs and Guards - Documented CI-style local Docker backend verification in release and Supabase runbooks. - Added release guard assertions for the new workflow and verifier behavior. ## Why - Move Docker-local Supabase validation into CI instead of requiring Docker Desktop on the Windows release workstation. ## Notes for Reviewers - Local validation covered the verifier static path, JSON parsing fixture, workflow YAML parsing, release guard tests, Dart format check, and git diff whitespace check.
## Summary - Handles Supabase CLI informational preamble before JSON backend-verification output. - Keeps CI all-pass enforcement for local Supabase backend checks. ## Changes Made ### Supabase Verification - Added JSON payload extraction before ConvertFrom-Json parsing. - Kept non-pass backend check failures fatal under -RequireAllPass. ### Release Guard Coverage - Extended source guard coverage for the parser helper. ## Why - GitHub Actions showed all Supabase backend checks passing, but the job failed because CLI preamble text preceded the JSON payload. ## Notes for Reviewers - Local parser smoke, SQL validation, Dart format, and release guard tests passed.
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.
Summary
supabase-local-validationGitHub Actions job that starts Supabase via Docker, resets the local database from tracked migrations, runs the backend verifier with JSON all-pass enforcement, uploads evidence, and stops the stack.scripts/verify_supabase_backend.ps1with-RequireAllPassand-OutFileso CI can fail on non-pass backend checks and archive non-secret evidence.Local verification
pwsh -NoProfile -File scripts/verify_supabase_backend.ps1 -ValidateOnlyflutter test test/scripts/release_guard_source_test.dartpwsh -NoProfile -File scripts/verify_dart_format.ps1flutter analyzeflutter testscripts/store_release_build.ps1 -Target Android -RunStrictAudit -EnvFile .env -SupportEmailVerifiedscripts/verify_store_artifacts.ps1 -Strict -RequireArtifact android-play-store-aab -RequireStrictAudit -RequireCurrentCommit