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 (825 forks)batch import
bughelp wanted

Repository metrics

Stars
 (7,442 stars)
PR merge metrics
 (No merged PRs in 30d)

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

Research direction
Inspect how standard version detects the latest version tag, specifically when prerelease tags exist. Ensure that merging a branch with prerelease tags correctly bumps to the next stable release, ignoring prerelease tags if desired.
Tech stack
javascriptnodejs
Domain
cli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65