fix: republish action

[MikeMcC399]

Issue

• Due to GitHub applying a secondary rate limit to the release job for PR fix(deps): update micromatch to 4.0.8 #1239, the release v6.7.3 is in an inconsistent state: it is shown on the releases list and on GitHub Marketplace, but the commits have not been copied to the v6 branch.
• This means that specifying cypress-io/github-action@v6 in workflows will use commit df7484c from release v6.7.2 instead of commit 57f6235 from v6.7.3
• A workaround is to explicitly use cypress-io/[email protected] (or the commit)

Change

An empty fix: commit is published to bump the release version to v6.7.4 and re-synchronize the v6 branch.

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[MikeMcC399]

@jennifer-shehane

Unfortunately the GitHub API quota was again exhausted and therefore the PR did not solve the issue of the unsynchronized v6 branch.

Request quota exhausted for request GET /search/issues

The options are:

1. Contact GitHub support and request assistance.
2. Push the commits to the v6 branch manually.
3. Wait until the next time a new version needs to be released and follow up then if it fails at that time.

[2:04:39 PM] [semantic-release] [@semantic-release/npm] › ℹ  Published @cypress/[email protected] to dist-tag @latest on https://registry.npmjs.org/
[2:04:39 PM] [semantic-release] › ✔  Completed step "publish" of plugin "@semantic-release/npm"
[2:04:39 PM] [semantic-release] › ℹ  Start step "publish" of plugin "@semantic-release/github"
[2:04:40 PM] [semantic-release] [@semantic-release/github] › ℹ  Published GitHub release: https://github.com/cypress-io/github-action/releases/tag/v6.7.4
[2:04:40 PM] [semantic-release] › ✔  Completed step "publish" of plugin "@semantic-release/github"
[2:04:40 PM] [semantic-release] › ℹ  Start step "success" of plugin "@semantic-release/github"
Request quota exhausted for request GET /search/issues
[2:04:40 PM] [semantic-release] › ✘  Failed step "success" of plugin "@semantic-release/github"
[2:04:40 PM] [semantic-release] › ✘  An error occurred while running semantic-release: RequestError [HttpError]: You have exceeded a secondary rate limit. Please wait a few minutes before you try again. If you reach out to GitHub Support for help, please include the request ID 1C90:1823:4815AC9:8AE1CDE:66CF2E78.
    at /home/runner/work/_actions/cycjimmy/semantic-release-action/v4/node_modules/@octokit/request/dist-node/index.js:112:21
    at process.processTicksAndRejections (node:internal/process/task_queues:[95](https://github.com/cypress-io/github-action/actions/runs/10598278439/job/29370524987#step:4:96):5)
    at async requestWithGraphqlErrorHandling (/home/runner/work/_actions/cycjimmy/semantic-release-action/v4/node_modules/@octokit/plugin-retry/dist-node/index.js:71:20)
    at async Job.doExecute (/home/runner/work/_actions/cycjimmy/semantic-release-action/v4/node_modules/bottleneck/light.js:405:18) {
  status: 403,
  response: {
    url: 'https://api.github.com/search/issues?q=repo%3Acypress-io%2Fgithub-action+type%3Apr+is%3Amerged+c47c901a25[99](https://github.com/cypress-io/github-action/actions/runs/10598278439/job/29370524987#step:4:100)f422565b5441a9b77cf63d7467d0+53c780cc5f4e19537af0f2be6be457a9445adbd0+06c5a7ba785340567add3ef10a6d749fc3242045',
Error: AggregateError: 
    HttpError: You have exceeded a secondary rate limit. Please wait a few minutes before you try again. If you reach out to GitHub Support for help, please include the request ID 1C90:1823:4815AC9:8AE1CDE:66CF2E78.
        at /home/runner/work/_actions/cycjimmy/semantic-release-action/v4/node_modules/@octokit/request/dist-node/index.js:112:21
        at async requestWithGraphqlErrorHandling (/home/runner/work/_actions/cycjimmy/semantic-release-action/v4/node_modules/@octokit/plugin-retry/dist-node/index.js:71:20)
        at async Job.doExecute (/home/runner/work/_actions/cycjimmy/semantic-release-action/v4/node_modules/bottleneck/light.js:405:18)
    status: 403,
    headers: {
      'access-control-allow-origin': '*',
      'access-control-expose-headers': 'ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset',
      'content-encoding': 'gzip',
      'content-security-policy': "default-src 'none'",
      'content-type': 'application/json; charset=utf-8',
      date: 'Wed, 28 Aug 2024 14:04:40 GMT',
      'referrer-policy': 'origin-when-cross-origin, strict-origin-when-cross-origin',
      server: 'github.com',
      'strict-transport-security': 'max-age=31536000; includeSubdomains; preload',
      'transfer-encoding': 'chunked',
      vary: 'Accept-Encoding, Accept, X-Requested-With',
      'x-content-type-options': 'nosniff',
      'x-frame-options': 'deny',
      'x-github-api-version-selected': '2022-11-28',
      'x-github-media-type': 'github.v3; format=json',
      'x-github-request-id': '1C90:1823:4815AC9:8AE1CDE:66CF2E78',
      'x-ratelimit-limit': '30',
      'x-ratelimit-remaining': '30',
      'x-ratelimit-reset': '1724853940',
      'x-ratelimit-resource': 'search',
      'x-ratelimit-used': '1',
      'x-xss-protection': '0'
    },
    data: {
      documentation_url: 'https://docs.github.com/free-pro-team@latest/rest/overview/rate-limits-for-the-rest-api#about-secondary-rate-limits',
      message: 'You have exceeded a secondary rate limit. Please wait a few minutes before you try again. If you reach out to GitHub Support for help, please include the request ID 1C90:1823:4815AC9:8AE1CDE:66CF2E78.'
    }
  },
  request: {
    method: 'GET',
    url: 'https://api.github.com/search/issues?q=repo%3Acypress-io%2Fgithub-action+type%3Apr+is%3Amerged+c47c901a2599f422565b5441a9b77cf63d7467d0+53c780cc5f4e19537af0f2be6be457a9445adbd0+06c5a7ba785340567add3ef10a6d749fc3242045',
    headers: {
      accept: 'application/vnd.github.v3+json',
      'user-agent': '@semantic-release/github v9.0.4 octokit-core.js/5.0.0 Node.js/20.13.1 (linux; x64)',
      authorization: 'token [REDACTED]'
    },
    request: { agent: undefined, hook: [Function: bound bound register] }
  },
  pluginName: '@semantic-release/github'
}

[jennifer-shehane]

weird...

[jennifer-shehane]

@MikeMcC399 Seems like semantic-release might have addressed this issue recently: semantic-release/github#857

Not sure if this is pulled into the action?

[MikeMcC399]

@jennifer-shehane

Thanks for digging up that information!

• fix: replace github search api with graphql in success lifecycle method semantic-release/github#857 released into @semantic-release/[email protected]
• @semantic-release/[email protected] is included in [email protected]. This is the latest available version of semantic-release and it is also the earliest version to include the fix. I had previously kept clear of v24 as it uses some beta versions and I thought it might be better to wait.

For the moment I suggest to wait. With the information that you discovered, we have something that we could try to migrate to if it turns out to be a blocker. Apparently this sporadic problem has been around for quite a long time, so it's strange that it has appeared twice in a row.

The logs show that we are picking up a default semantic-release version 21.1.2 since the workflow does not specify any particular version.