Repository navigation
README: install ops-get from v6.1.0; bump it on every release - #96
Merged
Merged
Conversation
README still pointed at v6.0.0 after v6.1.0. The hashes were right, since ops-get did not change, but the rule in CLAUDE.md read as optional in that case, while v5.0.2 and v6.0.0 both bumped README anyway. Make the bump an explicit every-release step. Closes #95
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.
Closes #95.
What changed
Why
The old wording ("update the hashes in README.md") read as optional when the hashes did not change, so v6.1.0 shipped without the bump.
Verified
From an empty directory, the README's own sh commands against v6.1.0:
and
sha256sum ops-get.ps1of the v6.1.0 asset:which matches the README's PowerShell hash.
Not verified
The PowerShell block itself was not run on Windows; only its hash was compared.