npm / p-retry
p-retry
What changed in p-retry 7 to 8, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-18.
2 breaking1 security1 new APIs and options3 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli initp-retry 86 changes
Breaking changes 2
Node.js 22 is now required to use p-retry.
Callbacks now run in the order shouldConsumeRetry, onFailedAttempt, then shouldRetry; consumption decisions precede failure notifications and retry decisions.
Security 1
Retry timing and callback validation were hardened.
New APIs and options 1
The onFailedAttempt context now includes retryDelay, making the retry delay available to the callback.
Fixes and other changes 2
Fixes an error related to invalid fractional retry counts.
TypeError retry handling was fixed.
p-retry 71 changes
Fixes and other changes 1
Fixes delayed abort when the signal is already aborted before the delay phase.