Repository navigation
Keep content refresh working after docs-only commits - #108
Merged
Merged
Conversation
A commit touching only release-ignored paths doesn't deploy, so the live backend stayed on the older SHA and every frontend refresh failed. Count the backend as current when it's behind main only by those paths. The release's final health check and page publication still need the exact SHA. Pin the Supabase CLI to 2.122.1. Version 3 rejects [inbucket] in supabase/config.toml, which broke manual releases at the migration step. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
RaviTejaKNTS
temporarily deployed
to
production
November 5, 2026 16:00 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
This branch was previously deployed
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.
Problem
PR #106 changed one line in
AGENTS.md. Docs-only commits don't release, so the live backend stayed onbfefafc5whilemainmoved tod44599f4.checkCurrentReleasethen failed every frontend content refresh, about every 2.5 minutes since 2026-11-05 10:56 UTC, withThe live backend SHA does not match current main.Running the release by hand also failed, at
Apply database migrations.setup-cliusesversion: latest, and Supabase CLI 3.0.0 (released 2026-11-02) rejects[inbucket]insupabase/config.tomlwithDbConfigLoadError. Push releases skip that step when no migration changed, so nothing showed it until now.Fix
checkCurrentReleasepasses when the live SHA is behindmainonly by files in the release'spaths-ignore, using the GitHub compare API. It fails closed onbehind,diverged, an empty or possibly truncated file list, or a rename out of a release-ignored path. A test keeps the list equal to the workflow.What stays exact
dokploy-release.mjs healthcheck.checkLiveRelease, used by page publication. So publishing pages after a docs-only commit still needs a release first; the release skill now says so.Not in this PR
Moving to CLI 3 needs
[inbucket]renamed to[local_smtp]and its own test.Merging this deploys
main, which also clears the current failure. A Sol review found no blocking issue.🤖 Generated with Claude Code