-
Notifications
You must be signed in to change notification settings - Fork 124
Closed
Description
semantic-release: 17.1.1
@semantic-release/npm: 7.0.5
npm: 7.0.0-beta.6
node: 12.18.3
{
"branch": "master",
"verifyConditions": [
"@semantic-release/changelog",
"@semantic-release/npm",
"@semantic-release/git",
"@qiwi/semantic-release-gh-pages-plugin"
],
"prepare": [
"@semantic-release/changelog",
"@semantic-release/npm",
"@semantic-release/git"
],
"publish": [
"@semantic-release/npm",
"@semantic-release/github",
"@qiwi/semantic-release-gh-pages-plugin"
]
}
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.
[4:19:52 PM] [semantic-release] › ℹ Start step "prepare" of plugin "@semantic-release/npm"
[4:19:52 PM] [semantic-release] [@semantic-release/npm] › ℹ Write version 2.0.4 to package.json in /home/travis/build/antongolub/yarn-audit-fix
npm ERR! Git working directory not clean.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/travis/.npm/_logs/2020-08-22T16_19_53_083Z-debug.log
[4:19:53 PM] [semantic-release] › ✔ Completed step "prepare" of plugin "@semantic-release/npm"
[1:56:32 PM] [semantic-release] [@semantic-release/git] › ℹ Prepared Git release: v2.0.0
[1:56:32 PM] [semantic-release] › ✔ Completed step "prepare" of plugin "@semantic-release/git"
[1:56:32 PM] [semantic-release] › ℹ Start step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[1:56:32 PM] [semantic-release] › ✔ Completed step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[1:56:37 PM] [semantic-release] › ✔ Created tag v2.0.0
[1:56:37 PM] [semantic-release] › ℹ Start step "publish" of plugin "@semantic-release/npm"
[1:56:37 PM] [semantic-release] [@semantic-release/npm] › ℹ Publishing version 2.0.0 to npm registry on dist-tag latest
npm notice
npm notice 📦 [email protected]
npm notice === Tarball Contents ===
npm notice 6.3kB CHANGELOG.md
npm notice 1.1kB LICENSE
npm notice 3.8kB README.md
npm notice 763B flow-typed/index.flow.js
npm notice 3.7kB package.json
npm notice 31B target/es5/cli.d.ts
npm notice 352B target/es5/cli.js
npm notice 370B target/es5/index.d.ts
npm notice 7.6kB target/es5/index.js
npm notice 647B target/es5/util.d.ts
npm notice 3.4kB target/es5/util.js
npm notice 31B target/es6/cli.d.ts
npm notice 256B target/es6/cli.js
npm notice 370B target/es6/index.d.ts
npm notice 4.1kB target/es6/index.js
npm notice 647B target/es6/util.d.ts
npm notice 2.1kB target/es6/util.js
npm notice 245B target/ts/cli.ts
npm notice 3.5kB target/ts/index.ts
npm notice 2.4kB target/ts/util.ts
npm notice 565B typings/index.d.ts
npm notice === Tarball Details ===
npm notice name: yarn-audit-fix
npm notice version: 1.6.1
npm notice filename: yarn-audit-fix-1.6.1.tgz
npm notice package size: 12.7 kB
npm notice unpacked size: 42.3 kB
npm notice shasum: dacff494bb5d5d47f69e3ca956a99c9cb6ab4163
npm notice integrity: sha512-QNGyysnyd52Ml[...]xJeS1NkOfWHtw==
npm notice total files: 21
npm notice
npm ERR! code E403
npm ERR! 403 403 Forbidden - PUT https://registry.npmjs.org/yarn-audit-fix - You cannot publish over the previously published versions: 1.6.1.
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy, or
npm ERR! 403 on a server you do not have access to.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/travis/.npm/_logs/2020-08-22T13_56_38_497Z-debug.log
[1:56:38 PM] [semantic-release] [@semantic-release/npm] › ℹ Published [email protected] to dist-tag @latest on https://registry.npmjs.org/
[1:56:38 PM] [semantic-release] › ✔ Completed step "publish" of plugin "@semantic-release/npm"
Metadata
Metadata
Assignees
Labels
No labels