chore(release): group the changelog and polish the README - #20
Merged
Conversation
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.
Prep for the v0.4.2 release. Two parts: release notes that are worth reading, and a README audit.
Release notes
changeloggained grouping, and the release body gained a header and an install footer. Verified by dry run (goreleaser release --skip=publish,announce), which caught three things I would otherwise have shipped blind:chore(release):leaked into the notes. The existing filter was^chore:, which does not match a scoped prefix. All five prefix filters now accept an optional scope.Fix segmentation fault ...subject, so Fix segmentation fault on invalid home-id in live command #17 landed under "Other changes" instead of "Bug fixes". The group regexps now match a bareFix/Featsubject case-insensitively, and a catch-all group guarantees nothing is silently dropped.abbrev: 7— GitHub autolinks 7+ char hashes in a release body, so each entry gets a clickable commit link.Rendered output for v0.4.2:
I also set
use: gitexplicitly rather thangithub. The compare API adds a network dependency that can fail a release for no real gain, and the local git log is reproducible in a dry run.README
powerctl.--home-idwas undocumented on bothliveandconsumption, despite being the flag at the centre of panic: segmentation fault inpowerctl livewith invalid home ID #13.invalid or non-existing home IDerror that Fix segmentation fault on invalid home-id in live command #17 introduced, so the message is greppable.1.0.0, which has never shipped.Verification
goreleaser checkpassesmake checkpasses (fmt, vet, mod verify, race tests)powerctl version→0.4.2⚡ Built on gilfoyle with Claude Code