Bump @octokit/plugin-retry from 6.0.1 to 7.2.0

[dependabot]

Bumps @octokit/plugin-retry from 6.0.1 to 7.2.0.

Release notes

Sourced from @​octokit/plugin-retry's releases.

v7.2.0

7.2.0 (2025-03-18)

Features

• don't retry on HTTP 410 (#621) (40a8c8b)

v7.1.4

7.1.4 (2025-02-14)

Bug Fixes

• deps: bump @​octokit/request-error from 6.1.6 to 6.1.7 [security] (#612) (62ae7c3)

v7.1.3

7.1.3 (2025-01-07)

Bug Fixes

• deps: bump octokit deps to fix Deno compat (#602) (b76ebd6)

v7.1.2

7.1.2 (2024-09-18)

Bug Fixes

• response.data.errors is sometimes empty (#577) (375b037), closes #536

v7.1.1

7.1.1 (2024-04-23)

Bug Fixes

• pkg: add a default fallback export (#542) (4cc1275)

v7.1.0

7.1.0 (2024-04-03)

Features

• security: Add provenance (#535) (dcf1fa3)

v7.0.4

7.0.4 (2024-04-03)

... (truncated)

Commits

• 40a8c8b feat: don't retry on HTTP 410 (#621)
• 470ac38 chore(deps): update dependency prettier to v3.5.3 (#618)
• 85a5c95 build(deps): lock file maintenance (#619)
• ea0d5d8 build(deps): lock file maintenance (#617)
• 4daf959 chore(deps): update dependency semantic-release-plugin-update-version-in-file...
• 33e0076 chore(deps): update dependency prettier to v3.5.2 (#616)
• 0d36408 build(deps): lock file maintenance (#614)
• 3770c90 build(deps): lock file maintenance (#611)
• 62ae7c3 fix(deps): bump @​octokit/request-error from 6.1.6 to 6.1.7 [security] (#612)
• 7c8a851 chore(deps): update dependency prettier to v3.5.1 (#610)
• Additional commits viewable 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

Summary by Sourcery

Enhancements:

• Upgrade @octokit/plugin-retry to the latest version, which includes a fix to prevent retrying requests that return a HTTP 410 status code.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the @octokit/plugin-retry dependency from version 6.0.1 to 7.2.0. The new version includes a feature that prevents retries on HTTP 410 errors.

Sequence diagram for retry logic with HTTP 410

sequenceDiagram
    participant Client
    participant Server

    Client->>Server: Send Request
    Server-->>Client: HTTP 410 Gone
    Client->>Client: Check if retry is needed
    alt HTTP 410
        Client->>Client: Do not retry
    else Other HTTP Errors
        Client->>Client: Retry Request
        Client->>Server: Send Request (Retry)
        Server-->>Client: Response
    end

Loading

File-Level Changes

Change	Details	Files
The @octokit/plugin-retry dependency was bumped from version 6.0.1 to 7.2.0.	Updated @octokit/plugin-retry to the latest version.	package.json package-lock.json
The new version of @octokit/plugin-retry introduces a feature that prevents retries on HTTP 410 errors.	The plugin will no longer retry requests that result in a 410 HTTP error.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!