conventional-changelog/standard-version

prerelease messes up with version bump

Open

#428 opened on Aug 7, 2019

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (7,442 stars) (825 forks)batch import
bughelp wanted

Description

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.

Contributor guide

Tech stack
javascriptnodejs
Domain
clireleasetooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic knowledge of semantic versioningFamiliarity with standard version CLIUnderstanding of Git tags
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
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.