8000 Failed step "success" of plugin "@semantic-release/github" · Issue #415 · semantic-release/github · GitHub
[go: up one dir, main page]
Skip to content

Failed step "success" of plugin "@semantic-release/github" #415

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
seanxu007 opened this issue Sep 21, 2021 · 16 comments
Closed

Failed step "success" of plugin "@semantic-release/github" #415

seanxu007 opened this issue Sep 21, 2021 · 16 comments

Comments

@seanxu007
Copy link

I ran npx semantic-release in my Github pipeline with my GITHUB_TOKEN.

Everything went well. A new tag is published, but there comes an error at the last step Failed step "success" of plugin "@semantic-release/github".

Logs show below:

image

Is there anyone who can help me~~ Thanks a lot~~
@josh-barker
Copy link
josh-barker commented Sep 21, 2021 •
edited by hearts bot
Loading

I have observed the same behaviour today.

@josh-barker
Copy link
josh-barker commented Sep 21, 2021 •
edited by hearts bot
Loading

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.

@skilbjo
Copy link
skilbjo commented Sep 21, 2021 •
edited by hearts bot
Loading

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

@krishna-acondy
Copy link
krishna-acondy commented Sep 21, 2021 •
edited by hearts bot
Loading

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! 🙏🏽

@krishna-acondy krishna-acondy mentioned this issue Sep 21, 2021
Closed
@ravali-rimmalapudi
Copy link
ravali-rimmalapudi commented Sep 21, 2021 •
edited by hearts bot
Loading

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

@RappC
Copy link
RappC commented Sep 21, 2021 •
edited by hearts bot
Loading

Seeing the same error.

@Spaideri
Copy link
Spaideri commented Sep 21, 2021 •
edited by hearts bot
Loading

Posting to raise priority, we are facing the same issue

@elektracodes
Copy link
elektracodes commented Sep 21, 2021 •
edited by hearts bot
Loading

Same error on multiple projects

@tentascoding
Copy link
tentascoding commented Sep 21, 2021 •
edited by hearts bot
Loading

Seeing the same error!

@tthyt
Copy link
tthyt commented Sep 21, 2021 •
edited by hearts bot
Loading

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.

@tthyt
Copy link
tthyt commented Sep 21, 2021 •
edited by hearts bot
Loading

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

@jamiecore jamiecore mentioned this issue Sep 21, 2021
Closed
3 tasks
@aanthonyrizzo
Copy link
aanthonyrizzo commented Sep 21, 2021 •
edited by hearts bot
Loading

I tried reverting to a previous release(semantic-release@17.4.7) 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.

@seanxu007
Copy link
Author
seanxu007 commented Sep 21, 2021 •
edited by hearts bot
Loading

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

@travi
Copy link
Member
travi commented Sep 21, 2021 •
edited by hearts bot
Loading

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.

@gr2m
Copy link
Member
gr2m commented Sep 21, 2021 •
edited by hearts bot
Loading

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.

@gr2m gr2m mentioned this issue Sep 21, 2021
Merged
4 tasks
@gr2m
Copy link
Member
gr2m commented Sep 21, 2021 •
edited by hearts bot
Loading

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

@gr2m gr2m closed this as completed Sep 21, 2021
@travi travi mentioned this issue Sep 22, 2021
Closed
@hashem78 hashem78 mentioned this issue Nov 12, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0