semantic-release: tag does already exists beta 20
Current behavior
I’m trying to update to semantic release beta. With beta 20 I successfully released a test package. Now I switched to a package which I have previously released with semantic-release@15. The updated semantic release now does not seem to detect my tags right:
I am fetching with: git fetch --tags ...
Expected behavior
should detect that I already published two releases. (v1.0.0, v1.0.1). This does work with semantic-release@15 with the same build setup
Environment
- semantic-release version: ^16.0.0-beta.20
- CI environment: Jenkins CI
- config
module.exports = {
plugins: [
'@semantic-release/commit-analyzer',
'@semantic-release/release-notes-generator',
[
'@semantic-release/npm',
{
pkgRoot: '.',
tarballDir: '.',
},
],
[
'@semantic-release/gitlab',
{
gitlabUrl: '...',
assets: [
{
path: '-*.tgz',
},
],
},
],
],
};
- CI logs:
[10:08:49 AM] [semantic-release] › ℹ Running semantic-release version 16.0.0-beta.20
[10:08:50 AM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/npm"
[10:08:50 AM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/gitlab"
[10:08:50 AM] [semantic-release] › ✔ Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[10:08:50 AM] [semantic-release] › ✔ Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[10:08:50 AM] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/npm"
[10:08:50 AM] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/npm"
[10:08:50 AM] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/gitlab"
[10:08:50 AM] [semantic-release] › ✔ Loaded plugin "addChannel" from "@semantic-release/npm"
[10:08:50 AM] [semantic-release] › ✔ Run automated release from branch master
[10:08:50 AM] [semantic-release] › ✔ Allowed to push to the Git repository
[10:08:50 AM] [semantic-release] › ℹ Start step "verifyConditions" of plugin "@semantic-release/npm"
[10:08:50 AM] [semantic-release] [@semantic-release/npm] › ℹ Verify authentication for registry release/
[10:08:50 AM] [semantic-release] › ✔ Completed step "verifyConditions" of plugin "@semantic-release/npm"
[10:08:50 AM] [semantic-release] › ℹ Start step "verifyConditions" of plugin "@semantic-release/gitlab"
[10:08:50 AM] [semantic-release] [@semantic-release/gitlab] › ℹ Verify GitLab authentication (/api/v4)
[10:08:50 AM] [semantic-release] › ✔ Completed step "verifyConditions" of plugin "@semantic-release/gitlab"
[10:08:50 AM] [semantic-release] › ℹ No git tag version found on branch master
[10:08:50 AM] [semantic-release] › ℹ No previous release found, retrieving all commits
[10:08:50 AM] [semantic-release] › ℹ Found 6 commits since last release
[10:08:50 AM] [semantic-release] › ℹ Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[10:08:50 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: Merge branch 'feature/semantic-release-update' into 'master'
ci: update sematic release to 16
See merge request !3
[10:08:50 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ The commit should not trigger a release
[10:08:50 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: ci: update semantic release to 16
[10:08:50 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ The commit should not trigger a release
[10:08:50 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: build: add commit npm script
[10:08:50 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ The commit should not trigger a release
[10:08:50 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: Merge branch 'bugfix/add-schema' into 'master'
fix(fnx-component): correctly reference schema in collection
See merge request !1
[10:08:50 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ The commit should not trigger a release
[10:08:50 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: fix(fnx-component): correctly reference schema in collection
[10:08:50 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ The release type for the commit is patch
[10:08:50 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: feat: initial commit
[10:08:50 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ The release type for the commit is minor
[10:08:50 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analysis of 6 commits complete: minor release
[10:08:50 AM] [semantic-release] › ✔ Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[10:08:50 AM] [semantic-release] › ℹ There is no previous release, the next release version is 1.0.0
[10:08:50 AM] [semantic-release] › ℹ Start step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[10:08:51 AM] [semantic-release] › ✔ Completed step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[10:08:51 AM] [semantic-release] › ℹ Start step "prepare" of plugin "@semantic-release/npm"
[10:08:51 AM] [semantic-release] [@semantic-release/npm] › ℹ Write version 1.0.0 to package.json in
v1.0.0
[10:08:51 AM] [semantic-release] [@semantic-release/npm] › ℹ Creating npm package version 1.0.0
npm notice
npm notice package: @1.0.0
npm notice === Tarball Contents ===
npm notice 1.5kB package.json
npm notice 1.4kB Jenkinsfile
npm notice 67B prettier.config.js
npm notice 639B README.md
npm notice 464B release.config.js
npm notice 604B tsconfig.json
npm notice 182B scripts/prerelease/commitId.js
npm notice 265B scripts/prerelease/lastTag.js
npm notice 915B scripts/prerelease/prerelease.js
npm notice 333B src/collection.json
npm notice 0 src/fnx-component/files/__name@dasherize__.component.__style__
npm notice 41B src/fnx-component/files/__name@dasherize__.component.html
npm notice 525B src/fnx-component/files/README.md
npm notice 11B src/fnx-component/index_spec.d.ts
npm notice 625B src/fnx-component/index_spec.js
npm notice 545B src/fnx-component/index_spec.js.map
npm notice 109B src/fnx-component/index.d.ts
npm notice 5.4kB src/fnx-component/index.js
npm notice 4.4kB src/fnx-component/index.js.map
npm notice 525B src/fnx-component/schema.json
npm notice === Tarball Details ===
npm notice name:
npm notice version: 1.0.0
npm notice filename: -1.0.0.tgz
npm notice package size: 6.5 kB
npm notice unpacked size: 18.6 kB
npm notice shasum: 91b17176827a6d17209a6a22a562b4925c52064b
npm notice integrity: sha512-nivompmrfEPn3[...]4VdCsziLfQauA==
npm notice total files: 20
npm notice
-1.0.0.tgz
[10:08:52 AM] [semantic-release] › ✔ Completed step "prepare" of plugin "@semantic-release/npm"
[10:08:52 AM] [semantic-release] › ✖ An error occurred while running semantic-release: { Error: Command failed: git tag v1.0.0 e76d5c745c506d0a5c61ecdfde5a4bb44f9c37d4
fatal: tag 'v1.0.0' already exists
at makeError (/node_modules/execa/index.js:174:9)
at Promise.all.then.arr /node_modules/execa/index.js:278:16)
at process._tickCallback (internal/process/next_tick.js:68:7)
code: 128,
stdout: '',
stderr: 'fatal: tag \'v1.0.0\' already exists\n',
failed: true,
signal: null,
cmd: 'git tag v1.0.0 e76d5c745c506d0a5c61ecdfde5a4bb44f9c37d4',
timedOut: false,
killed: false }
{ Error: Command failed: git tag v1.0.0 e76d5c745c506d0a5c61ecdfde5a4bb44f9c37d4
fatal: tag 'v1.0.0' already exists
at makeError (/node_modules/execa/index.js:174:9)
at Promise.all.then.arr /node_modules/execa/index.js:278:16)
at process._tickCallback (internal/process/next_tick.js:68:7)
code: [33m128[39m,
stdout: [32m''[39m,
stderr: [32m'fatal: tag \'v1.0.0\' already exists\n'[39m,
failed: [33mtrue[39m,
signal: [1mnull[22m,
cmd: [32m'git tag v1.0.0 e76d5c745c506d0a5c61ecdfde5a4bb44f9c37d4'[39m,
timedOut: [33mfalse[39m,
killed: [33mfalse[39m }npm ERR! code ELIFECYCLE
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 2
- Comments: 16 (8 by maintainers)
I’m guessing it’s because
+refs/heads/${branch}:refs/heads/${branch}
was replaced by+refs/heads/${branch}:refs/remotes/upstream/${branch}
. @jmodjeski75 what is the reason for this change?