Skip to content

docs: changelog for v0.5.4#365

Merged
dpup merged 1 commit into
mainfrom
changelog-v0.5.4
Jun 1, 2026
Merged

docs: changelog for v0.5.4#365
dpup merged 1 commit into
mainfrom
changelog-v0.5.4

Conversation

@dpup
Copy link
Copy Markdown
Collaborator

@dpup dpup commented Jun 1, 2026

Summary

Cut v0.5.4 from Unreleased. Three Claude Code fixes:

#361 (CI Node 24 bump) is internal-only and intentionally not in the release notes.

Test plan

  • CHANGELOG renders correctly with new v0.5.4 section
  • Merge, then tag v0.5.4 from main to trigger the goreleaser workflow

@claude
Copy link
Copy Markdown

claude Bot commented Jun 1, 2026

Claude finished @dpup's task in 1m 11s —— View job


Code Review

  • Gather context
  • Read CHANGELOG.md diff
  • Check against docs/STYLE-GUIDE.md
  • Post review findings

Changelog entry looks solid. Structure is correct: ## Unreleased is empty (ready for the next cycle), the ## v0.5.4 section immediately follows with the summary paragraph and ### Fixed entries, all three entries follow the "Fix X — previously, Y happened when Z" pattern from CLAUDE.md, and every entry has a PR link. Voice is active, language is factual and specific throughout.

One minor inaccuracy to consider:

Summary paragraph vs. detailed entry — "space" is omitted

The summary says:

workspaces with . or _ in the path

The detailed entry says (correctly):

For any workspace path containing a ., _, or space (e.g. a macOS username like user.name)

The summary silently drops "or space" from the affected character set. Since anyone scanning the summary to decide if they're affected would miss the space case, it's worth adding for accuracy.

Suggested fix: Fix this →

Everything else looks good to merge.

@dpup dpup merged commit e051df6 into main Jun 1, 2026
4 checks passed
@dpup dpup deleted the changelog-v0.5.4 branch June 1, 2026 18:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant