[GH-ISSUE #395] 0.11.6 is a breaking change, patches should never be breaking changes #125

Closed
opened 2026-02-27 20:23:15 +03:00 by kerem · 4 comments
Owner

Originally created by @ForsakenHarmony on GitHub (Mar 15, 2023).
Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/395

Running cargo update should never cause breaking changes

Please adhere to semver if you publish to crates.io (or well not necessarily semver, because that allows breaking on patch, rust does not)

Originally created by @ForsakenHarmony on GitHub (Mar 15, 2023). Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/395 Running `cargo update` should never cause breaking changes Please adhere to semver if you publish to [crates.io](https://crates.io/) (or well not necessarily semver, because that allows breaking on patch, rust does not)
kerem 2026-02-27 20:23:15 +03:00
Author
Owner

@ForsakenHarmony commented on GitHub (Mar 15, 2023):

alternatively, please publish v1.0.0

<!-- gh-comment-id:1469087221 --> @ForsakenHarmony commented on GitHub (Mar 15, 2023): alternatively, please publish `v1.0.0`
Author
Owner

@blueforesticarus commented on GitHub (May 26, 2023):

It is pre-1.0, so it is actually a minor revision bump.

<!-- gh-comment-id:1564419482 --> @blueforesticarus commented on GitHub (May 26, 2023): It is pre-1.0, so it is actually a minor revision bump.
Author
Owner

@github-actions[bot] commented on GitHub (Nov 23, 2023):

Message to comment on stale issues. If none provided, will not mark issues stale

<!-- gh-comment-id:1823740624 --> @github-actions[bot] commented on GitHub (Nov 23, 2023): Message to comment on stale issues. If none provided, will not mark issues stale
Author
Owner

@ForsakenHarmony commented on GitHub (Jan 23, 2024):

strongly disagree as cargo, npm and others will update anything after the first non 0 in the version number without asking

just use the first non 0 number in the version for breaking changes, not anything after

<!-- gh-comment-id:1906920049 --> @ForsakenHarmony commented on GitHub (Jan 23, 2024): strongly disagree as cargo, npm and others will update anything after the first non 0 in the version number without asking just use the first non 0 number in the version for breaking changes, not anything after
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/rspotify#125
No description provided.