what stackpulse tracks
npm releases from GitHub
StackPulse watches npm release notes and keeps the original source link close to every summary.
#stacks/
loading releases…
releases
breaking
security
deprecated
migrations
The package manager for JavaScript StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches npm release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This release includes bug fixes for pack and owner commands, updates documentation regarding a breaking change in npm 12, and updates several dependencies.
Users affected by the unknown-config breaking change in npm 12 may need to review their configurations.
Review configurations if experiencing issues related to unknown-config settings.
This release removes npm shrinkwrap and updates Node.js version support. It also includes improvements to the release process.
Users relying on shrinkwrap functionality or running unsupported Node.js versions are affected.
Migrate from shrinkwrap to package-lock.json and verify Node.js version compatibility.
This release introduces breaking changes related to Node.js version support and includes a feature to trigger the release process.
Users running Node.js versions outside the specified range will be affected.
Ensure your Node.js version is compatible with the new requirements.
This release introduces breaking changes by updating the supported Node.js versions. It also includes a feature to trigger the release process.
Users running Node.js versions outside the specified range will be affected.
Ensure your Node.js version is within the supported range (`^22.22.2 || ^24.15.0 || >=26.0.0`).
This major release introduces significant breaking changes including JSON output format changes, removal of legacy commands, and updated default behaviors. Key changes involve package management, git handling, and dependency resolution.
All users of npm CLI are affected, particularly those using JSON output, shrinkwrap files, man pages, or legacy commands.
Review breaking changes and update your npm workflows accordingly before upgrading.