👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

Please don't use 11.3.1

It's a special back port release for CJS users, which is not published to the main npm tag

The proper release to use is 11.3.0

@wolfy1339 that didn't solve anything. the package managers will resolve it to version v11.3.1 (at least pnpm)

You can force your package manager to use whichever version you want. In the end you can manually edit your lockfile and package.json to suit your needs.

I triggered a new release that should fix the issue

🎉 This issue has been resolved in version 11.3.3 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

Thank you for quick response and the new release!

Writing overrides in package.json resolved the problem for now:

{
  "pnpm": {
    "overrides": {
      "@octokit/plugin-paginate-rest": "11.3.0",
      "@octokit/plugin-rest-endpoint-methods": "13.2.1"
    }
  }
}

The new release also works.
A new release for plugin-rest-endpoint-methods would also be helpful.

fyi, @viceice it's probable best not to have semantic-release in your dependencies, but rather use a tool like npx

It avoids all issues like this and any compability issues that arise when you use different Octokit versions that what semantic-release usees

fyi, @viceice it's probable best not to have semantic-release in your dependencies, but rather use a tool like npx

It avoids all issues like this and any compability issues that arise when you use different Octokit versions that what semantic-release usees

That would make things more complicated, because we need a lot plugins, which are not installed by default.

We install plugins as devDependencies but not the core semantic-release packages here in Octokit

That would make things more complicated, because we need a lot plugins, which are not installed by default.

I install plugins as needed as part of the release workflow. I wish there was something like releaseDependencies