Repository navigation
ci: check once a day that production runs the deploy the repository records - #943
Merged
Merged
Conversation
…ecords check-deployed.mjs --against-lock compares, on every public name: the coordinator's commit (by prefix; a dirty build never matches) and creation protocol with the deploy engine/versions.lock records on staging; the relay's source digest with relay-server --digest built at that commit, naming the likely cause when they differ; the web's version.json with the tip of main and the latest release version; and each coordinator and relay preflight with the custom headers the app sends it. Any difference fails the run; staging is reported and never fails it. A daily workflow runs it. Read-only on every host. Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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 & why
A daily check that production runs the deploy the repository records, instead of only probing whether a named route exists.
node scripts/check-deployed.mjs --against-lock --relay-digest=<16 hex>compares, on every public name:-dirtybuild never matches) and the creation protocol it expects, with the[deploy_build]commitengine/versions.lockrecords onstaging(where the lock PRs land) and theMIN_CREATIONthat commit ships;source_digestwithrelay-server --digestbuilt at that commit (the relay's own rule, never re-implemented), naming the likely cause when they differ;version.jsonwith the tip ofmain(what Vercel publishes) and the version in itsui/package.json;Any difference fails the run; the staging coordinator is reported and never fails it. The rules live in
scripts/what-is-running.mjsand are tested (ui/src/what-is-running.test.ts);scripts/against-lock.mjsgathers git and the hosts' answers. TheWhat is runningworkflow runs it daily (read-only, no secrets, 15-minute timeout, no persisted credentials).DEPLOY.mdsays the schedule starts once the workflow reachesmain, and that the check is red by design between a deploy and the lock PR that records it.Today it is green on all 13 rows.
Verify-before-finishing checklist
pnpm -C ui exec vitest run src/what-is-running.test.tspasses (18 tests); each comparison red-checked by mutationpnpm -C ui exec tsc -bcleantype(scope): description;no-changelog(CI and scripts only)Co-Authored-By: Claude <noreply@anthropic.com>, no session link