fix(deps): update dependency @octokit/types to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@octokit/types	^8.0.0 -> ^9.0.0

---

Release Notes

octokit/types.ts

v9.0.0

Compare Source

Features

• many unreleased changes to endpoint types (#​501) (dcfb6f3), closes #​499

BREAKING CHANGES

• remove defunct endpoints that no longer exist

v8.2.1

Compare Source

Bug Fixes

• revert "feat: many unreleased endpoint updates (#​499)" (fcbd164)

v8.2.0

Compare Source

Features

• many unreleased endpoint updates (#​499) (d952319)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[gr2m]

@octokit/js-community any idea why these errors pop up now?

I feel like it must be related to octokit/types.ts#501 but the PR doesn't show any changes?

The endpoint is still in @octokit/types and also in @octokit/openapi-types. Did something change that might prevent setting the 2nd argument for some endpoints? It's very odd

[wolfy1339]

I feel like it must be related to octokit/types.ts#501 but the PR doesn't show any changes?

It was an empty commit to trigger a major version bump.
The actual PR that merged in the changes was octokit/types.ts#499

The endpoint is still in @octokit/types and also in @octokit/openapi-types. Did something change that might prevent setting the 2nd argument for some endpoints? It's very odd

That is odd. I don't understand why that would happen only for some endpoints and not every one

[wolfy1339]

$ npm ls @octokit/types
@octokit/[email protected]
├─┬ @octokit/[email protected]
│ └── @octokit/[email protected]
├─┬ @octokit/[email protected]
│ ├─┬ @octokit/[email protected]
│ │ └── @octokit/[email protected]
│ └── @octokit/[email protected]
├── @octokit/[email protected]
└─┬ [email protected]
  └─┬ @semantic-release/[email protected]
    └─┬ @octokit/[email protected]
      ├─┬ @octokit/[email protected]
      │ ├─┬ @octokit/[email protected]
      │ │ └── @octokit/[email protected]
      │ ├─┬ @octokit/[email protected]
      │ │ └── @octokit/[email protected]
      │ └── @octokit/[email protected]
      ├─┬ @octokit/[email protected]
      │ └── @octokit/[email protected]
      └─┬ @octokit/[email protected]
        └── @octokit/[email protected]

This is most likely why

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[wolfy1339]

I upgraded the dependencies on @octokit/request, @octokit/request-error and updated the lock file to use a newer version of @octokit/endpoint

The problems are now resolved

[gr2m]

thank you!

[github-actions]

🎉 This PR is included in version 2.0.5 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀