-
Notifications
You must be signed in to change notification settings - Fork 79
Open
Description
The following construct results in a wrong prerelease version and thus a failing job, as the tag already exists.
Steps to reproduce:
master
taggedv1.0.0
, fast forwarded fromdevelop
- commit feature on
develop
-> Commit is taggedv1.1.0-develop.1
- create branch
release/test-release
fromdevelop
-> Same commit is taggedv1.1.0-rc.1
- commit feature on
develop
->fatal: tag 'v1.1.0-develop.1' already exists
Expected Behavior: Tag v1.1.0-develop.2
instead of v1.1.0-develop.1
The previous prerelease version does not seem to be recognized, although it was tagged. Maybe this is caused by the commit being tagged twice? This case should be accounted for. Or am I doing something wrong?
Error log Context:
[semantic-release] › ℹ Found git tag v1.0.0 associated with version 1.0.0 on branch develop
[semantic-release] › ℹ Found 2 commits since last release
[semantic-release] › ℹ Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: feat: conflicting feature
[semantic-release] [@semantic-release/commit-analyzer] › ℹ The release type for the commit is minor
[semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: feat: add gitignore
[semantic-release] [@semantic-release/commit-analyzer] › ℹ The release type for the commit is minor
[semantic-release] [@semantic-release/commit-analyzer] › ℹ Analysis of 2 commits complete: minor release
.releaserc.json
{
"branches": [
{"name": "master"},
{"name": "develop", "prerelease": "develop"},
{"name": "release/*", "prerelease": "rc"}
],
"plugins": [
["@semantic-release/commit-analyzer", {
"preset": "angular"
}],
"@semantic-release/release-notes-generator",
["@semantic-release/exec", {
"publishCmd": "echo ${nextRelease.version} > .version"
}],
"@semantic-release/gitlab"
]
}
kengoldfarb, carmanchris31, akccakcctw and jorroll
Metadata
Metadata
Assignees
Labels
No labels