Request quota exhausted causes GH Action to hang

[kallioaleksi]

Hi,

I'm running semantic-release as a part of our deployment workflow, and finally got it configured, but when it runs it hangs while searching for issues. This is the first run so if it's trying to find an issue for each commit it found since the previous release (never), it's going to have a lot to check.

We don't even use issues in Github, so the optimal solution would be a config setting to skip searching for issues altogether.

[...]
[1:23:38 PM] [semantic-release] › ✔  Created tag v1.0.0-beta.1
[1:23:38 PM] [semantic-release] › ℹ  Start step "publish" of plugin "@semantic-release/github"
[1:23:38 PM] [semantic-release] [@semantic-release/github] › ℹ  Published GitHub release: https://github.com/myorg/myrepo/releases/tag/v1.0.0-beta.1
[1:23:38 PM] [semantic-release] › ✔  Completed step "publish" of plugin "@semantic-release/github"
[1:23:38 PM] [semantic-release] › ℹ  Start step "success" of plugin "@semantic-release/github"
Request quota exhausted for request GET /search/issues
Request quota exhausted for request GET /search/issues
Request quota exhausted for request GET /search/issues
Request quota exhausted for request GET /search/issues
Request quota exhausted for request GET /search/issues
[...]

[babblebey]

Hi @kallioaleksi,

Could you kindly share more information on this...

• Your Configuration
• semantic-release version you're consuming

I'd like to understand this some bit more, but kindly note this....

• Issues are only looked up in the "success" step of this plugin if it seen in the release commits body/messages, so things like Fixes/Closes #23 means that issue would be looked up to use in the release step
• Issues and PR are treated as "issues" here too as much as GitHub describes them

[kallioaleksi]

Hi @babblebey,

Here's the configuration:

"release": {
  "branches": [
    {
      "name": "env/prod",
      "channel": "latest",
      "prerelease": false
    },
    {
      "name": "env/dev",
      "channel": "beta",
      "prerelease": "beta"
    }
  ],
  "plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    "@semantic-release/github",
    "@semantic-release/git"
  ]
}

We're consuming semantic-release version 22.0.12, @semantic-release/github@9.2.6 and @semantic-release/git@10.0.1.

It seems that it's tagging every single PR with the message "This PR is included in release vx.x.x 🎉 ", we're changing our merge process in deployments to maintain release history better and reduce how much back it has to look.