Repository navigation
nuxt-cloudflare: cache restore for extra-gate and preview; drop retired Blacksmith/lightweight runs-on arms - #249
Merged
narduk-durable-agent-sessions[bot] merged 2 commits intoNov 10, 2026
Conversation
Both jobs ran a package install with no cache restore while build, checks, e2e, deploy-dry-run and fast restore node-deps-<os>-<arch>-<pm>-<lockfile>. Add the same restore-only pair (resolve directory, restore) before the install. No second save: build owns the default-branch write. Hosted runners only, as everywhere else (R8). Refs narduk-enterprises/fleet#1431 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Blacksmith was disabled 2026-10-06 (D-BLACKSMITH-7) and the lightweight class retired 2026-10-13 (D-RUNNER-LIGHTWEIGHT-RETIRE-1). Delete the runs-on arms keyed on vars.BLACKSMITH_RUNNERS_ENABLED, vars.BLACKSMITH_LINUX_LABEL and vars.CI_LIGHTWEIGHT_RUNNER, their comment blocks, and the README text documenting them. With those variables unset every job resolves exactly as before (110160 old-vs-new evaluations, 0 mismatches). CI_LINUX_RUNNER, the lightweight-runner input and the caller-supplied "blacksmith- predicates are untouched. Tests that asserted the variables now assert they are ignored. Refs narduk-enterprises/fleet#1431 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
narduk-durable-agent-sessions
Bot
force-pushed
the
stop-two-wasted-dependency-i-1419
branch
from
November 10, 2026 15:03
a12a677 to
35fa367
Compare
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.
Refs narduk-enterprises/fleet#1431
Two commits: A (dependency-cache restore) and B (dead routing arms).
A.
extra-gateandpreviewrestore the dependency cacheBoth jobs ran
pnpm install/npm ciwith no restore, whilebuild,checks,e2e,deploy-dry-runandfastrestorenode-deps-<os>-<arch>-<pm>-<lockfile hash>. Each now gets the same restore-only pairchecksuses, beforeConfigure package registry auth. Nocache/savewas added:buildowns the default-branch write.The
if: runner.environment == 'github-hosted'guard is the repo's rule R8 (a self-hosted guest's package store is shared and persistent; tarballing it is unsound), so the restore only helps hosted runners, i.e. public callers. A private caller on self-hostedlinux-ciskips both steps by design. That is the same behaviour the other jobs have.B. Blacksmith and lightweight arms removed from
runs-onRemoved: every arm keyed on
vars.BLACKSMITH_RUNNERS_ENABLED,vars.BLACKSMITH_LINUX_LABELandvars.CI_LIGHTWEIGHT_RUNNER(56runs-onlines), the Blacksmith-overflow comment blocks, the stale "Blacksmith since 2026-09-29" comment inred-main-listener.yml, and the README text that documented them as live. Tests that asserted the variables now assert they are ignored.Before/after,
red-main-listener.ymljobreconcile(the shortest case):before (2347 chars)
Not changed:
CI_LINUX_RUNNER(live), thelightweight-runnercaller input (a breaking-input removal,test_nuxt_input_freeze.pypins it), and thestartsWith(<input or CI_LINUX_RUNNER>, '"blacksmith-')predicates. Those accept a caller-supplied or live-variable label, so deleting them changes resolution if any caller passes one. Follow-up, needs a caller survey.Verification
runs-onexpressions at the pre-B commit and now, evaluated with the interpreter fromscripts/test_runner_default.pyover visibility true/false/missing x 8 event shapes (PR, draft, Dependabot, lane bot, T2 repo, schedule, nightly dispatch, push) x 5CI_LINUX_RUNNERvalues x runner-input variants (default, linux-ci, other fleet, blacksmith label, ubuntu-latest, self-hosted string/array/object, macOS) xfast-parallel/preview-checks/production-output-directory, with the three retired variables empty: 110160 evaluations, 0 mismatches. (The harness found two real bugs in my first rewrites before this run.)scripts/precheckat a12a677 (the head 35fa367 adds only comment edits, after which actionlint,lint_callables.pyand the six routing tests were re-run green): exit 0, 43 PASS lines (native-alerts actionlint build 0.27s, actionlint 2.33s,lint_callables.py1.03s, everyscripts/test_*.pyincludingtest_actionlint_native_permissions.pyandtest_runner_default.py59s).test_runner_default.py,test_cache_paths.py(13 cache sites, 0 failures),test_apple_gate.py,test_reusable_browser_tests.py,test_preview_gate.py,test_production_upload.py.Assumed
Org variables are unreadable from here: assumed
BLACKSMITH_RUNNERS_ENABLEDandCI_LIGHTWEIGHT_RUNNERare unset or false in every caller repo (Blacksmith disabled 2026-10-06, D-BLACKSMITH-7; lightweight class retired 2026-10-13, D-RUNNER-LIGHTWEIGHT-RETIRE-1). A caller that still sets either now gets the default route instead of the dead one.🤖 Generated with Claude Code