release: bump 0.1.2 -> 0.1.3 - #123
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cuts 0.1.3 across the twenty version-bearing files this repository writes itself, and closes the changelog gap the previous release left open.
Changelog
[Unreleased]became[0.1.3]. One entry was missing from it and is added here: thewickra-corelockfile refresh from #122. The two entries already there -- the benchmarks pom that tracked a version deleted two releases ago (#121) and the publish gate that read a pending CI run as a failed one (#120) -- carry over unchanged.Everything merged since v0.1.2 is now described.
git log v0.1.2..mainlists exactly those three commits.Bump
Run through
bump_version.py, which reports 21 declarations rewritten: the workspaceCargo.toml,Cargo.lockvia a realcargo build, the Python, Node (package, six platform stubs, lockfile, and the napi loader's version literal), Java, C# and R manifests, both poms that resolve the binding,CITATION.cffincluding its release date, andSECURITY.md's supported-version table.scripts/check_version_sync.pyagrees on all 21. The benchmarks pom is among them for the first time -- it was added to that check in #121, which is why this bump moves it rather than leaving it behind as 0.1.1 and 0.1.2 did.A grep for
0.1.2outside the changelog returns one hit,iana-time-zone-haiku, whose own version happens to be the same string.Verification
cargo fmt --all-- no changescargo test --workspace --all-features-- all suites passcargo clippy --workspace --all-targets --all-features -- -D warnings-- clean