chore: run the action on node24, refresh v12 backlog
Post-v11 cleanup
Small follow-ups found by checking the shipped state against the repo. No user-facing behavior change.
Action runs on node24
Both manifests declared using: "node20". GitHub already force-migrates node20 actions and warns on every run:
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24
The bundle targets node22+, so node24 is pinned explicitly in action.yml and packages/action/action.yml. Verified against the docs that node24 is a supported runs.using value, and smoke-tested the built bundle end-to-end on a modern runtime:
exit: 0
✅ Minification complete! 31.3% reduction in 9ms
var g=function(n){return"hi "+n};
The composite action at .github/actions/node-minify/action.yml is using: composite and unaffected.
v12 backlog corrected
It had drifted from the code it describes:
- Item 1 listed deprecated type-alias detection as outstanding, but v11 shipped it — along with
@node-minify/runandengines.nodescanners. Only the GCC runtime guidance remains. - It stated the compressor registry carries the GCC caveat via a
notesfield.CompressorEntryhas onlyname,status,packageNameand optionalreplacement— there is nonotesfield, so a v12 implementer would have gone looking for something that doesn't exist. - Post-release ops listed all 5 removed compressors as pending npm deprecation. Checked the registry: all 5 are already deprecated with replacement messages. Only
@node-minify/runis still undeprecated.
Also recorded the two release traps this cycle exposed, so they aren't rediscovered at v12:
GITHUB_TOKENcannot create a tag whose tree adds.github/workflows/*, so the major tag needed a manual pushscripts/publish.tscatches everynpm publisherror as "may already exist" and exits 0 — a real failure is indistinguishable from a no-op
Verification
| Gate | Result |
|---|---|
| build | pass |
| lint / typecheck | pass |
| test | 1047 passed (70 files) |
| removed-compressor guard | pass |
action manifests parse, using=node24 | pass |
| action bundle minifies end-to-end | pass |
Needs your npm credentials
@node-minify/run was removed in v11 but still installs silently at 10.5.0. I'm not authenticated to npm locally, so this one is yours:
npm deprecate @node-minify/run "@node-minify/run was removed in v11. It was an internal Java/process-spawn helper with no public replacement; remove it from your dependencies."
Summary by cubic
Pins the GitHub action to node24 in both manifests and corrects the v12 backlog doc to match what v11 actually shipped.
- GitHub force-migrates node20 actions to node24 with warnings on every run; the bundle already targets node22+, so this removes the warnings.
- The backlog wrongly listed deprecated type-alias detection as outstanding (v11 shipped it), claimed a
notesfield that doesn't exist onCompressorEntry, and listed all 5 removed compressors as pending deprecation when only@node-minify/runremains. - Records two release traps for v12:
GITHUB_TOKENcan't create a tag that adds workflow files, andscripts/publish.tslogs publish failures but exits 0, so CI can't distinguish a real failure from a no-op.
@node-minify/run still installs silently at 10.5.0; deprecating it requires npm credentials.
Summary by CodeRabbit
- Updates
- Upgraded the GitHub Action runtime from Node.js 20 to Node.js 24.
- Documentation
- Updated the v12 backlog to reflect completed v11 work and current release-operation items.