release: add 0.3.0 changelog entry - #326
Merged
evanpurkhiser merged 1 commit intoAug 7, 2026
Merged
Conversation
evanpurkhiser
deleted the
evanpurkhiser/release-add-0-3-0-changelog-entry
branch
August 7, 2026 15:31
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.
Craft's
simplechangelog policy requires a section matching the version being released —findChangesetis called withfallbackToUnreleased = falsefor anything that isn'tauto, socraft prepare 0.3.0throwsNo changelog entry found for version "0.3.0"without this. Same shape as #297 for 0.2.0.Covers the two user-facing changes since 0.2.0: the package rename, and the conflicting-Claude-plugin cleanup from #322. #321 (build harnesses on demand) is an internal refactor with no user-visible effect, so it gets no entry.