Release 0.10.0 - #110
Merged
Merged
Conversation
All eight version strings and the four lockfiles. The release guard checks two of them (issue #77), so the rest are by hand and by eye, and `cargo build --locked` was run afterwards since that is what `make cli/release` uses and a drifted lockfile fails there first. Minor rather than patch. The three fixes since v0.9.0 are fixes, but #75 changes behaviour a user can notice: `collapse compress notes.txt -f tar -o mixed.zip` used to succeed and now refuses, because the file it produced was a tar named `.zip` that this same CLI would not extract.
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
1 participant
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.
Version bump only. Twelve files, all of them the bump.
Why minor rather than patch
The three changes since v0.9.0 are fixes, but #75 changes behaviour a user can notice:
A command that used to succeed now refuses. That belongs in a minor, not a patch.
What is in it
#75 above.
#67. The CLI answered with a path nobody typed.
collapse compress ./sub/a.txtreported/Users/…/scratch/sub/a.txt.zip. Both spellings are kept now: the resolved one still drives the guards, the engine and the arcname, and the typed one is what gets reported.#93. tar did not say which entry it could not write. Issue #64's guarantee reached zip and 7z but not tar's untouched-name branch, the one nearly every archive takes. Its error also needed unwrapping first, since it arrives as three wrappers each repeating the destination.
Verification
620 Rust tests and 116 Vitest, all suites green locally,
cargo build --lockedclean after the bump. No stray files: the working tree at commit time was exactly the twelve version sites, which is the checkbad.zipearned in v0.9.0.Closing keywords are on the dev-into-main PR and in the commits of #109; the default branch is
main, so they fire there.