It might seem like common sense that if a version changes, then something in the code changes, but there are nuances.
For instance there might be branding strategies like bumping a product version to a new major early or there might side effects of bundling components where we make an increment on one of the components, but all others are bumped just because they belong to the same global package.
I've looked at the spec and I've only seen that if something changes, then it MUST be versioned, but haven't seen the opposite. If something hasn't changed, CAN it be versioned?
Originally created by @pak3nuh on GitHub (Feb 22, 2022).
Original GitHub issue: https://github.com/semver/semver/issues/807
It might seem like common sense that if a version changes, then something in the code changes, but there are nuances.
For instance there might be branding strategies like bumping a product version to a new major early or there might side effects of bundling components where we make an increment on one of the components, but all others are bumped just because they belong to the same global package.
I've looked at the spec and I've only seen that if something changes, then it MUST be versioned, but haven't seen the opposite. If something hasn't changed, CAN it be versioned?
Yes, a change is not required - although bumping a version when no change is included causes churn for consumers, and so may be seen as a hostile act if done frequently.
<!-- gh-comment-id:1047944758 -->
@ljharb commented on GitHub (Feb 22, 2022):
Yes, a change is not required - although bumping a version when no change is included causes churn for consumers, and so may be seen as a hostile act if done frequently.
I think this is not something to clarify on the semver specification, so just closing in favor of the above answer.
<!-- gh-comment-id:1214172483 -->
@JohnTitor commented on GitHub (Aug 13, 2022):
I think this is not something to clarify on the semver specification, so just closing in favor of the above answer.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @pak3nuh on GitHub (Feb 22, 2022).
Original GitHub issue: https://github.com/semver/semver/issues/807
It might seem like common sense that if a version changes, then something in the code changes, but there are nuances.
For instance there might be branding strategies like bumping a product version to a new major early or there might side effects of bundling components where we make an increment on one of the components, but all others are bumped just because they belong to the same global package.
I've looked at the spec and I've only seen that if something changes, then it MUST be versioned, but haven't seen the opposite. If something hasn't changed, CAN it be versioned?
@ljharb commented on GitHub (Feb 22, 2022):
Yes, a change is not required - although bumping a version when no change is included causes churn for consumers, and so may be seen as a hostile act if done frequently.
@JohnTitor commented on GitHub (Aug 13, 2022):
I think this is not something to clarify on the semver specification, so just closing in favor of the above answer.