chore(deps): bump p-retry from 7.1.1 to 8.0.0

[dependabot]

Bumps p-retry from 7.1.1 to 8.0.0.

Release notes

Sourced from p-retry's releases.

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

---

sindresorhus/p-retry@v7.1.1...v8.0.0

Commits

• 35681f6 8.0.0
• 9d47b60 Harden retry timing and callback validation
• f011d2e Fix TypeError retry handling
• 85cdece Require Node.js 22
• 616306e Change retry callback order
• 96cce98 Add retryDelay to onFailedAttempt context
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 87ca184

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.14%. Comparing base (955e6b9) to head (87ca184).
⚠️ Report is 3 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2698   +/-   ##
=======================================
  Coverage   89.14%   89.14%           
=======================================
  Files          65       65           
  Lines       10361    10361           
  Branches      473      473           
=======================================
  Hits         9236     9236           
  Misses       1094     1094           
  Partials       31       31           

Flag	Coverage Δ
cli-hooks	89.14% <ø> (ø)
cli-test	89.14% <ø> (ø)
logger	89.14% <ø> (ø)
oauth	89.14% <ø> (ø)
socket-mode	89.14% <ø> (ø)
web-api	89.14% <ø> (ø)
webhook	89.14% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.