Repository navigation
chore(security): override undici to 6.29.1 (RQ-9393 follow-up) - #121
Conversation
release-it 19.2.4 pins undici to exactly 6.23.0, which opened 14 undici Dependabot alerts (4 High) once #120 merged. Force the patched 6.29.1: same major, published >14 days ago. release-it 20.x pins undici 7.24.5 (also vulnerable) and 21.x needs Node ^22.22.2, so an override is the smallest fix. npm audit high/critical by root advisory, before -> after: undici removed, nothing added. Runtime packages unchanged vs master. Verified on Node 22 and 24: npm ci, build, dist/ byte-identical to master, all dist require() calls resolve, release dry-run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
commit: |
Why
#120 upgraded
release-itto 19.2.4 so thatengine-strictworks on Node 24. That version pinsundicito exactly 6.23.0, which is vulnerable. When #120 merged, 14undiciDependabot alerts (4 High) opened in this repo. This PR fixes that regression.What
overrides: { "undici": "6.29.1" }: the patched release in the same major asrelease-it's pin, published more than 14 days ago.Why an override and not a
release-itbump:release-it20.x pinsundici7.24.5, which is also vulnerable.^22.22.2and a changelog-plugin major upgrade.undicihere is only used by the dev release tooling; runtime packages are unchanged vsmaster.Verified locally
npm ci(with.npmrc)npm run build(tsc)dist/vsmasterrequire()indist/resolvesnpm auditHigh/Critical, by root advisory:undiciis removed and nothing is added. The remaining roots (axios,form-data,lodash,node-forge,ws,picomatch,basic-ftp) were all there before and are tracked separately (runtime: RQ-9394).🤖 Generated with Claude Code
Summary by CodeRabbit