-
Notifications
You must be signed in to change notification settings - Fork 114
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.
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
Plugin considers the release successful but received 403 from npm #269
Comments
Out of hand, I couldn't say what's going on here, I'm afraid. If you can setup a test repository that reproduces the problem I can have a look, otherwise I won't be able to help |
Sure. Here's the repo: antongolub/yarn-audit-fix. The only is needed to reproduce the issue is just to remove/disable As you can see, yaf uses node@7.0.0-beta.5 as its own dep, so semrel-npm actually invokes the same bin during release. const result = execa(npm, ['publish', basePath, '--userconfig', npmrc, '--tag', distTag, '--registry', registry], {
cwd,
env,
}); |
I was not able to reproduce your problem, not using npm anyway
The npm resolution should use it's own dependency if there is a version conflict, I have no idea what is going on here for you, but I think it's a bug with yarn. Can you check in with them? |
I've also tried to run release through npx. For example, commit antongolub/yarn-audit-fix@e450f9e |
Try to setup your repository from scratch. Don't use yarn, use npm to install dependencies. Then run |
Perhaps this is due to the work of Travis CI environment.
if not, npm version is 6.14.6.
|
Thanks for the help. I'm closing this for now. |
|
semantic-release: 17.1.1
@semantic-release/npm: 7.0.5
npm: 7.0.0-beta.6
node: 12.18.3
travis#376481822 and same with DEBUG travis#376491345
I assume this problem may be caused by npm v7-beta, but the release should crash on errors anyway.
The text was updated successfully, but these errors were encountered: