mirror of
https://github.com/ramsayleung/rspotify.git
synced 2026-04-26 07:55:55 +03:00
[GH-ISSUE #395] 0.11.6 is a breaking change, patches should never be breaking changes #125
Labels
No labels
Stale
bug
discussion
enhancement
good first issue
good first issue
help wanted
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/rspotify#125
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ForsakenHarmony on GitHub (Mar 15, 2023).
Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/395
Running
cargo updateshould never cause breaking changesPlease adhere to semver if you publish to crates.io (or well not necessarily semver, because that allows breaking on patch, rust does not)
@ForsakenHarmony commented on GitHub (Mar 15, 2023):
alternatively, please publish
v1.0.0@blueforesticarus commented on GitHub (May 26, 2023):
It is pre-1.0, so it is actually a minor revision bump.
@github-actions[bot] commented on GitHub (Nov 23, 2023):
Message to comment on stale issues. If none provided, will not mark issues stale
@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