actions/ci-cd
3
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(bump): Schutz vor Doppel-Tags nur für Tags derselben Art
ci/woodpecker/pr/plugins Pipeline was successful
Details
ci/woodpecker/push/plugins Pipeline was successful
Details

Browse Source 
Ein dev-Tag auf dem Commit darf nach einem Fast-Forward-Merge in einen
Release-Branch das Beta-Tag nicht verhindern.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
tuandClaude Fable 5.1 committed 2026-10-31 10:50:47 +01:00
1 parent 035550e183
commit 53906fdf14
2 files changed
+15 -7
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

README.md
+1 -1
View File
@@ -182,7 +182,7 @@ Derives the next version for the pushed branch and pushes it as a tag on the tri
If the stable tag of a line exists (`v2.4.0` after the release), the next patch of that line is used (`v2.4.1-beta.0`, `v2.4.1-dev.…`).
Only the commit that triggered the pipeline is tagged; if the branch moved on, the step exits without a tag and the newer pipeline takes over. A commit that already carries a `v*` tag is not tagged again, so a re-run does not build twice.
Only the commit that triggered the pipeline is tagged; if the branch moved on, the step exits without a tag and the newer pipeline takes over. A commit that already carries a tag of the same kind (dev, beta or stable) is not tagged again, so a re-run does not build twice; a dev tag does not block the beta tag after a fast-forward merge.
Settings: