v4.0.0
⚠️ Breaking changes
The action now runs on the node24 runtime and requires Node >= 22.12.0.
action.yml moves from using: node16 to using: node24. node16 is
end-of-life, and puppeteer-core 25 requires Node >= 22.12.0, so node20 was no
longer viable either.
Before upgrading, check that:
- Self-hosted runners are on a runner release that supports the
node24
runtime. Older runners will fail to start the action. - Linux self-hosted runners have glibc 2.28 or newer. Node 24 binaries
will not run on older glibc (RHEL/CentOS 7 and Ubuntu 18.04 are below this).
GitHub-hosted runners already satisfy both.
Features
- Add Trivy results to the scan (#544ffd6)
Maintenance
This release covers 59 commits since v3.0.4 (April 2023). Highlights:
- Test suite restored on modern Node. Built-in TypeScript type-stripping (on by
default since Node 22.6) preempted ts-node'srequire.extensionshook, which
broke the suite with a misleadingCannot find module ./src/pdf/pdfWriter. - CI now runs the suite against Node 22, 24 and 26.
npm run packageis the single source of truth fordist/; CI uses the
pinnednccdevDependency rather than installing latest globally.- Dependency updates:
puppeteer-core21 → 25,@actions/coreand
@actions/io→ v2,commander11 → 15,jsdom23 → 28,marked4 → 10,
chai4 → 6,mocha10 → 11,@vercel/ncc0.38 → 0.45, ESLint 9 with flat
config and neostandard. - Security: resolved all
npm auditfindings by overriding mocha's transitive
diffandserialize-javascript(GHSA-73rr-hh4g-fpgx, GHSA-5c6j-r48x-rmvq,
GHSA-qj8w-gfj5-8c6v). Replaced the unmaintainedts-sinonwithsinon22. - CodeQL analysis re-enabled and scoped to
src/, excluding the generated
dist/bundle.
Removed
-
The Build Bundle Executables workflow. It invoked
npm run build-exe-*
scripts that were dropped in April 2023, so it had failed immediately for over
three years. No release ever carried these binaries — v3.0.0 through v3.0.4 all
have zero attached assets.Note:
README.mdstill contains "Installation" and "Running" sections that
describe downloading a zip bundle and running./github-security-report-mac-x64.
Those instructions were already inaccurate before this release and remain to be
cleaned up.