Repository navigation
Release 0.7.0, withdrawing 0.6.1 - #16
Merged
Merged
Conversation
Same code as 0.6.1 under a number that does not understate it. Making scan history opt in changes a default, and someone upgrading on a patch would have found `bootintel history` silently stopped recording. The policy at the top of CHANGELOG.md reserves PATCH for changes with no user-visible behaviour change, which that is not. I said so when cutting 0.6.1 and was asked to renumber. "Retag" is not literally possible for the crates.io half. A version there can be yanked but never reused, so withdrawing 0.6.1 means publishing a new number and retiring the old one across every channel: yank on crates.io, the GitHub release kept for the record but no longer marked latest, and the Homebrew formula moved forward. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Same code as 0.6.1 under a number that does not understate it.
Making scan history opt in changes a default, and someone upgrading on a patch would have found
bootintel historysilently stopped recording. The policy in CHANGELOG.md reserves PATCH for changes with no user-visible behaviour change."Retag" is not literally possible for the crates.io half. A version there can be yanked but never reused, so withdrawing 0.6.1 means publishing a new number and retiring the old one across every channel: yank on crates.io, the GitHub release kept for the record but no longer marked latest, and the Homebrew formula moved forward.
310 tests pass, clippy clean under
-D warnings, rustfmt clean.