conventional-changelog/standard-version

prerelease messes up with version bump

Open

#428 建立於 2019年8月7日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)JavaScript (7,442 star) (825 fork)batch import
bughelp wanted

描述

When I do a pre-release i.e. on a dev branch

yarn standard-version --no-verify --prerelease integration --skip.changelog --skip.commit

Which is fine, it released correctly to v2.0.0-integration.0 with a breaking change

However, when I merge from integration branch to master

It didn't pick it up as v2.0.0 instead it picked it up as v1.11.3 which is weird, however when I remove the previous tag locally tag -d v2.0.0-integration.0 and ran a dry-run

it picked it up correctly as tagging release v2.0.0 which is correct.

So I assumed the prerelease versioning in the tag is not being parsed properly? Otherwise, if we can ignore it would be good also. Thanks.

貢獻者指南

技術棧
javascriptnodejs
領域
clireleasetooling
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Basic knowledge of semantic versioningFamiliarity with standard version CLIUnderstanding of Git tags
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
Investigate the logic in standard version's codebase that determines the next version based on existing tags, focusing on how prerelease tags (e.g., v2.0.0 integration.0) are parsed and whether they are incorrectly included or excluded when computing the next main release. Look at the function that reads the latest tag and the bump algorithm, likely in files such as `lib/lifecycle.js` or `src/index.js`. Reproduce the issue with a similar scenario to identify whether the parsed prerelease version is not being properly ignored or reset after merging.