Repository navigation
chore: cut CHANGELOG for v0.1.1 - #22
Merged
Merged
Conversation
Moves the five commits landed since v0.1.0 out of [Unreleased] and into a 0.1.1 section. One genuine bugfix (#10, PR #21: concurrent first use opened a firmware session per caller); the other four commits are README work across PRs #18, #19, #20, folded into three Documentation entries since #18 landed as two commits on one topic. No code changes — CHANGELOG.md only. The tag is not created here; that is a separate step from a clean main per CONTRIBUTING.md "Releases". Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdds a ChangesRelease notes
Estimated code review effort: 1 (Trivial) | ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
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.
What
Moves the five commits that landed since
v0.1.0out of[Unreleased]and into a## [0.1.1] - 2026-07-30section, leaving[Unreleased]empty above it.CHANGELOG.mdonly — no code, config, or workflow changes.Entries
Read each commit and its PR rather than paraphrasing subject lines:
2c0c25ce09679d,5f6613c09b07675aa793bPR #18 landed as two commits on one topic (the initial Claude Code setup section plus the review follow-up that hardened it), so they are folded into a single entry — four docs commits, three entries.
Two judgment calls worth a look:
### Documentationas a subsection. Keep a Changelog's canonical set is Added/Changed/Deprecated/Removed/Fixed/Security. README-only changes aren't "Changed" functionality, and 0.1.0 already uses a non-canonical### Notes, so a descriptive subsection fits the file's existing style. Say the word if you'd rather these sit underChangedor drop out entirely.#10,#9, …). The 0.1.0 section carries no references — it had nothing to point at. Easy to strip if you want the file reference-free.Voice, subsection style, and ~79-column wrapping follow the 0.1.0 section.
Verification
All five CI tasks, run locally:
One local snag worth recording: the first
mise run lintreported 10 issues in../fix-token-double-login/..., a sibling worktree that no longer exists. Stale golangci-lint cache holding diagnostics keyed to deleted paths —golangci-lint cache cleanclears it and the run is green. Nothing to fix in the repo; noting it in case it shows up in another worktree.Not done here
No tag. Per CONTRIBUTING.md "Releases", tagging is a separate step from a clean
mainafter this merges, and the tag push is what triggersrelease.yml/ GoReleaser.🤖 Generated with Claude Code