Skip to content

docs: regenerate the mock/ snapshots so the daily release guard passes - #978

Merged
HugoXK merged 1 commit into
mainfrom
dev1/mock-snapshot-refresh
Nov 17, 2026
Merged

HugoXK merged 1 commit into
mainfrom
dev1/mock-snapshot-refresh

Conversation

@HugoXK

@HugoXK HugoXK commented Nov 17, 2026

Copy link
Copy Markdown
Owner

Written-by: Fledge Platform Dev-1

No-issue: regenerate the generated mock/ snapshots, which the daily release refuses to run on top of when they are stale.

The daily release failed before it could plan the day: run 44027318332 on 4cfe2986, job plan the daily minor release and push its branch, ##[error] mock/ is stale: run npm run mock:snapshot, commit mock/ in a docs pull request, and re-run the release; the tag job was skipped, so no release happened. This PR regenerates them from the current UI. Ten files change and every one of them is under mock/; nothing else is touched, and no scratch file, dist/, tmp/ or log is staged.

Tip at publication: 4b0f06e7b97480e0826fbb3dd8fcb7b8f36fb296, tree a3e73030c44fb61969e49db883ec91654da0f4a1, parent c3d16bbc51bc04e0fc405f1f4e6c0e7bc1868439. 10 files, +303/−217, all mock/.

Ran:

  • npm ci; npm run mock:snapshot — wrote 12 files, 10 changed
  • npm run check — exit 0, 2610/2610

Not run: Docker image, real SMTP.

Risk: T2 — mock/ is not a named path in the risk rules, so it takes the T2 default: risk-tier: T2; basis: mock/add-repository.html.
Rollback: revert the squash commit; the snapshots return to the previous generation and the release guard goes back to refusing.
Docs-not-needed: this is the generated artifact itself, not a document about it.
Changelog-not-needed: regenerated snapshots of existing pages, with no user-visible behaviour change.

@HugoXK-bot HugoXK-bot left a comment •

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: PASS at 4b0f06e
Written-by: HugoXK-bot
Author: Fledge Platform Verdict

  • Scope is exactly the ten generated files: the API lists 10 changed paths and every one is under mock/ (mock/assets/app.css:16, mock/add-repository.html:7-10), all modifications, none added or deleted, and no source, workflow, script or changelog file moves.
  • These are the snapshots the current UI generates, checked two ways: at this tip npm run mock:snapshot writes 12 files and leaves a clean tree (0 diff over the 804 tracked files), and on live main c3d16bbc (this PR's base) the same command writes a mock/ that is byte-identical to this PR's (diff -r reports nothing) while npm run mock:check on that base fails — exactly the staleness the PR removes.
  • The guard this unblocks is npm run mock:check itself (.github/workflows/daily-release.yml:367-369); at this tip it passes (mock-snapshot: ok (12 files), exit 0), and the copied asset is byte-identical to public/app.css with every page pinned to version eed2b384789d.
  • Tip 4b0f06e7 is 10 files +303 −217, all under mock/; live main equals the base c3d16bbc, so the generation ran against current main rather than an older tree.
  • At this tip every check is green except review-gate, which fails only because no verdict existed at it (ci-ok, test (24), lint, typecheck, build, risk, pr-lint success; action-pins is skipped for a docs-only diff).

Ran: npm run mock:snapshot at the tip (12 files written; git diff empty afterwards), npm run mock:check at the tip (ok (12 files), exit 0), npm run mock:snapshot on c3d16bbc then diff -r against this tip's mock/ (identical), npm run mock:check on c3d16bbc (exit 1 — the stale state this fixes).
Not run: Docker image, real SMTP; no live database or release run was touched.

Review id: 5934576010

@HugoXK
HugoXK merged commit 9094444 into main Nov 17, 2026
34 of 35 checks passed
@HugoXK
HugoXK deleted the dev1/mock-snapshot-refresh branch November 17, 2026 07:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants