Repository navigation
feat: X-Git-Sha response header with the deployed commit - #496
Merged
Merged
Conversation
Lets the test suite tell which commit is live on dev and prod, like the backend's /health/ git_sha. Baked at build time from GITHUB_SHA, so a rolled-back release reports its own commit.
This was referenced Oct 7, 2026
This branch was successfully 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
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.
Why
CivicDataSpace-test's
deployed_prgate needs to know which frontend commit is live, so tests for a merged PR run only once it's actually deployed. The frontend has no equivalent of the backend's/health/git_sha. Inferring it from the GitHub workflow-runs API failed: during some windows, lasting a minute or more, that endpoint returns a weeks-old run list.Change
next.config.mjsheaders()addsX-Git-Sha: <GITHUB_SHA>on every path when the build hasGITHUB_SHA, which GitHub Actions always sets. The existingX-Robots-Taglogic is unchanged.The value is fixed at build time, so each release under
releases/reports its own commit, and a rollback reports the commit actually being served.Verified (local
next build+next start)/enFEATURE_SITEMAPS='true'),GITHUB_SHA=111…GITHUB_SHAX-Git-Sha: 111…, noX-Robots-Tag'false'),GITHUB_SHA=222…GITHUB_SHA=9999X-Git-Sha: 222…,X-Robots-Tag: noindex, nofollowThe commit SHA is already public for the backend via
/health/.