NEC-107: Take the pending action majors, and stop naming pnpm twice #169

Merged
nectenda-agent merged 6 commits from worktree-renovate-batch-node26 into main 2026-09-25 14:59:42 +01:00
Collaborator

Task: NEC-107 — https://projectron.nerchure.com/tasks/107

Six action majors that Renovate has been holding on the dependency dashboard
(#18), plus the three things Renovate cannot do for them.

The references. Every actions/*, pnpm/action-setup and docker/*
reference under .forgejo/ moves to its current major, and so do the three in
the public mirror's generated GitHub workflow. The census is 9 checkout@v7,
6 setup-node@v7, 4 action-setup@v6, 4 cache@v6, 2 buildx@v4,
1 qemu@v4 — 26 sites, none left at an older major. The count is the thing to
check rather than the diff: this branch was written against 16 sites, main
added three workflows carrying 7 more, and merging it unchanged would have left
Renovate to re-offer the stragglers.

version: goes with the bump, at 4 sites. pnpm/action-setup@v6 reads
packageManager and fails a run that names pnpm twice — we found that the
expensive way, on a red run. The mirror's generator is the one that mattered
most: it writes the mirror's packageManager from this repository's, so
bumping it without dropping version: would have failed in the public
repository rather than here.

Two claims that had stopped being true. pnpm.onlyBuiltDependencies is
gone from the root package.json — pnpm 12 prints that it ignores the field on
every install, and it had drifted, naming sqlite3 (not a dependency) and
omitting the three packages allowBuilds denies. And "Node 26 cannot build
better-sqlite3" is withdrawn from deploy/inventory.mjs,
deploy/UPGRADES.md, docs/plan-master.md and docs/plan-phase0.md. Two
tests now read that wording from POLICY.node.lineNote instead of copying it;
a grep for the wording missed one of them twice, and CI caught what the grep
did not. Both are mutation-checked in each direction.

What this run does not cover. checkpoint-soak.yml and e2e-soak.yml are
dispatch-only, so their bumps are unexercised here. The mirror's workflow
reaches GitHub only on the next plugin publish; build-mirror --check proves
it stages consistently, not that GitHub accepts it.

Changelog

NONE

Task: NEC-107 — https://projectron.nerchure.com/tasks/107 Six action majors that Renovate has been holding on the dependency dashboard (#18), plus the three things Renovate cannot do for them. **The references.** Every `actions/*`, `pnpm/action-setup` and `docker/*` reference under `.forgejo/` moves to its current major, and so do the three in the public mirror's generated GitHub workflow. The census is 9 `checkout@v7`, 6 `setup-node@v7`, 4 `action-setup@v6`, 4 `cache@v6`, 2 `buildx@v4`, 1 `qemu@v4` — 26 sites, none left at an older major. The count is the thing to check rather than the diff: this branch was written against 16 sites, `main` added three workflows carrying 7 more, and merging it unchanged would have left Renovate to re-offer the stragglers. **`version:` goes with the bump, at 4 sites.** `pnpm/action-setup@v6` reads `packageManager` and fails a run that names pnpm twice — we found that the expensive way, on a red run. The mirror's generator is the one that mattered most: it writes the mirror's `packageManager` from this repository's, so bumping it without dropping `version:` would have failed in the *public* repository rather than here. **Two claims that had stopped being true.** `pnpm.onlyBuiltDependencies` is gone from the root `package.json` — pnpm 12 prints that it ignores the field on every install, and it had drifted, naming `sqlite3` (not a dependency) and omitting the three packages `allowBuilds` denies. And "Node 26 cannot build better-sqlite3" is withdrawn from `deploy/inventory.mjs`, `deploy/UPGRADES.md`, `docs/plan-master.md` and `docs/plan-phase0.md`. Two tests now read that wording from `POLICY.node.lineNote` instead of copying it; a grep for the wording missed one of them twice, and CI caught what the grep did not. Both are mutation-checked in each direction. **What this run does not cover.** `checkpoint-soak.yml` and `e2e-soak.yml` are dispatch-only, so their bumps are unexercised here. The mirror's workflow reaches GitHub only on the next plugin publish; `build-mirror --check` proves it stages consistently, not that GitHub accepts it. ## Changelog NONE
cruelacid force-pushed worktree-renovate-batch-node26 from bbc92e28ab
All checks were successful
Release note / release-note (pull_request) Successful in 13s
e2e / multi (push) Successful in 4m30s
CI / build (pull_request) Successful in 4m43s
CI / e2e (pull_request) Successful in 5m14s
CI / promote (pull_request) Has been skipped
to c30b165c00
All checks were successful
Release note / release-note (pull_request) Successful in 13s
CI / build (pull_request) Successful in 4m31s
CI / e2e (pull_request) Successful in 5m6s
CI / promote (pull_request) Has been skipped
Deploy site / deploy (push) Successful in 58s
e2e / multi (push) Successful in 4m36s
CI / build (push) Successful in 5m1s
CI / e2e (push) Successful in 5m17s
CI / promote (push) Successful in 31s
2026-09-25 14:53:42 +01:00
Compare
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Nectenda/nectenda!169
No description provided.