What changed in p-retry from 7 to 8

2 releases numbered after v7.1.1 up to and including v8.0.1, stable releases only. v7.1.1 and v8.0.1 are the newest stable releases of 7 and 8 we track; this page follows them as new ones ship.

6 changes across 2 releases

Added 1

v8.0.0

  • Add retryDelay to onFailedAttempt context
Changed 2

v8.0.0

  • Change retry callback order from onFailedAttempt → shouldConsumeRetry → shouldRetry to shouldConsumeRetry → onFailedAttempt → shouldRetry
  • Harden retry timing and callback validation
Fixed 2

v8.0.1

  • Fix error for invalid fractional retry counts

v8.0.0

  • Fix TypeError retry handling
Removed 1

v8.0.0

  • Drop support for Node.js versions below 22

Original release notes, newest first

The list above is our reading of these notes; the originals from Sindre Sorhus are here, one fold per release.

v8.0.1
  • Fix error for invalid fractional retry counts 3c22035

https://github.com/sindresorhus/p-retry/compare/v8.0.0...v8.0.1

View originalPermalink

v8.0.0
Breaking
  • Require Node.js 22 85cdece
  • Change retry callback order 616306e
    • Callback order changed from onFailedAttempt → shouldConsumeRetry → shouldRetry to shouldConsumeRetry → onFailedAttempt → shouldRetry.
    • Consumption decisions are now made before failure notifications and retry decisions.
Improvements
  • Add retryDelay to onFailedAttempt context (#66) 96cce98
  • Fix TypeError retry handling f011d2e
  • Harden retry timing and callback validation 9d47b60

https://github.com/sindresorhus/p-retry/compare/v7.1.1...v8.0.0

View originalPermalink