-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
version bumps for v1.3.0 #1345
Comments
starting with #1238 we need to bump MINOR for |
this one is breaking CI (it requires a MAJOR bump to |
this one is breaking CI (it requires a MAJOR bump to |
need to bump MINOR on |
moving Sv1 example inside the not sure if this even deserves a version bump? just taking note here anyways |
moving not sure if this even deserves a version bump? just taking note here anyways |
in #1455 CI is forcing us to bump MAJOR for multiple crates:
|
in #1459 CI is forcing us to bump MAJOR in |
#1442 introduces breaking changes into |
unfortunately
cargo semver-checks
will only warn us about MAJOR bumps, but MINOR and PATCH bumps still require our own disciplinein the past we had some discussions about bumping MINOR and PATCH crate versions on the same PR that introduces the changes, or right before doing the release
there's pros and cons with both strategies
if we bump on the same PR that introduces the changes:
crates.io
(e.g.: 1.2.0 then 1.4.0)if we bump right before the release:
a good compromise is to keep a dedicated issue to keep track of changes for every release
every time we introduce some change, we take note here
and then before we do the release, we use this issue to analyze all the needed version bumps before publishing the crates
we should use this issue to keep track of the needed version bumps before v1.3.0
The text was updated successfully, but these errors were encountered: