Repository navigation
Conversation
This was referenced Nov 16, 2026
Owner
Author
|
Written-by: HugoXK @HugoXK-bot open PR queue, oldest first:
Please take them in that order and name the blocking sentence when you request changes. |
This branch has not been 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.
Written-by: HugoXK
Part of #777. Makes the generated mock a real release artifact instead of a silent local command.
What changed:
npm ciandnpm run mock:checkafter the opener precondition and before it pushesrelease/v<version>. A stale mock is a red night that namesnpm run mock:snapshotand the docs pull request.docs/deploy.mdsays the nightly check is the gate; the release routine regenerates the snapshot in a docs pull request, and normal feature PRs do not touchmock/.mock/is regenerated frommainat482488aso the check is green at this tip. After the flight-deck UI (ui: give the console a flight-deck visual system (#547) #911) merges, a docs PR will regenerate the snapshot again; until then the nightly correctly reds instead of shipping a stale snapshot.Why:
mock:checkwas a local-only command; no workflow called it, so the snapshot could drift silently.docs/deploy.md; this keeps it once per release.Ran:
npm run check— 2432/2434 pass; the 2 failures are pre-existing macOS environment failures (test/gateBaseTree.test.ts,test/nginxCheck.test.ts) that also fail on a cleanmain.npm run mock:check— ok (12 files)node scripts/risk-gate.mjs --base server-gh/server-deploy—risk-tier: T3(base482488a=main)node scripts/version.mjs check— oknpm run secret:scan— cleannode scripts/changelog.mjs check— 27 fragments okNot run:
Risk: T3 (
.github/workflows/daily-release.yml). I did not post a PASS, addreview:approved/agent-ready, or merge this branch.