I have observed the same behaviour today.

I also found that if I used curl with my token, I'm able to get the issue details using the endpoint in the error.
That leads me to believe it could be a timing issue.

I am getting a similar (although not exact) error in cycjimmy/semantic-release-action#80

We've also started having this exact same issue in https://github.com/sasjs/cli.

https://github.com/sasjs/cli/runs/3660512107

Any help on this would be great, thank you! 🙏🏽

I am also getting the same error today semantic-release/git#298

Seeing the same error.

Posting to raise priority, we are facing the same issue

Same error on multiple projects

Seeing the same error!

I was able to work around this error by suppressing the success commenting in .releaserc

        [
            "@semantic-release/github",
            {
                "successComment": false
            }
        ],

That way the problematic issue search query is skipped and the GH release can be created at least.

This seems to be related octokit/rest.js#114

I tried reverting to a previous release([email protected]) and that did not seem to fix the issue either. I did not try earlier releases but it seems @tthyt has the only current workaround.

Thank you @tthyt, to pass over it will be a great solution currently~

Are folks still seeing this failure? I did see this happen with one of my projects last night, but have seen several releases complete successfully today with the default config. If this was just an API problem that has been fixed, I would like to close this issue. If folks are still seeing this happen, we can keep it open until we understand better.

I was trying to reproduce the problem in octokit/rest.js#114 but to no avail either. I also did several releases myself with both semantic-release 17 & 18 today and have not seen the error.

Mystery solved, please update your lock files, make sure you don't have node-fetch v2.6.3 in there
node-fetch/node-fetch#1301