You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge main into staging to resolve conflicts with commit message release: merging main -> staging , hash is xyz
Commit xyz in staging has a release and beta tag/release created
Checkout main git merge --ff-only staging, rc tag/release created
Merge squashed PR commit into staging, semantic-release errors with tag already exists
Showing the notes for that commit git notes --ref semantic-release show xyz | cat results in {"channels":["rc"]} which should be {"channels":["rc", "beta"]}
Expected behavior
Subsequent commits into staging do not cause a duplicate tag error.
It happens to us as well when we fast-forward merge a higher branch (e.g. develop) into a pre-release branch, hence a backmerge. The pre-release branch release job overwrites channel info created by previous develop release job.
In get-release-to-add.js it looks like pre-release branches are ignored, which cause the channel overwrite instead of adding to the current content.
consthigherChannels=branches// Consider only releases of higher branches.slice(branches.findIndex(({ name })=>name===branch.name)+1)// Exclude prerelease branches.filter(({ type })=>type!=="prerelease").map(({ channel })=>channel||null);
Is it intentional to work like this?
Update:
Just read release notes for v23 and noticed that there is one note reference per tag. We are using v21 with a single reference.
Shouldn't this change prevent channel overwrite?
Current behavior
Given the following branching strategy.
staging (default branch, channel: beta) -> main (channel: RC) -> LTS
Expected behavior
Subsequent commits into staging do not cause a duplicate tag error.
semantic-release
version21.1.1
CI environment
Github Actions
Plugins used
These are documented in in the config below.
semantic-release
configurationCI logs
Show notes before action
Show notes after action
The text was updated successfully, but these errors were encountered: