Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Version 1.2.0 #199

Merged
merged 1 commit into from Jan 28, 2020
Merged

Version 1.2.0 #199

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion Cargo.toml
View file
Open in desktop
@@ -1,6 +1,6 @@
[package]
name = "smallvec"
version = "1.1.0"
version = "1.2.0"
Copy link
Member

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?

Copy link
Collaborator Author

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.

edition = "2018"
authors = ["Simon Sapin <simon.sapin@exyr.org>"]
license = "MIT/Apache-2.0"
Expand Down