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 1.2.0 #199
Version 1.2.0 #199
Conversation
@@ -1,6 +1,6 @@ | |||
[package] | |||
name = "smallvec" | |||
version = "1.1.0" | |||
version = "1.2.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, actually, does this need to be a breaking release?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In semver, for stable releases (version >= 1.0.0), the first number (MAJOR) is incremented for breaking changes. The second number (MINOR) is incremented for additional features added without breaking backward compatibility. The third number (PATCH) is incremented for bug fixes that do not add new API or break existing API.
Cargo treats two versions as "compatible" if the first non-zero component is the same. So 0.1.0 to 0.2.0 is a breaking change, but 1.1.0 to 1.2.0 is not.
Ah, nice, I always forget. @bors-servo r+ |
📌 Commit 04d54bd has been approved by |
☀️ Test successful - checks-travis |
Changes in this release:
IntoIter
now implementsDebug
(impl Debug for IntoIter #196).smallvec!
macro is now easier to use inno_std
contexts where thevec!
macro isn't automatically imported (Use full path to vec! in smallvec! macro #198).