docs(changelog): curate and date the v0.2.4 release section#287
Merged
Conversation
Curate the full [0.2.4] changelog from all PRs merged since v0.2.3 and set the release date. Refs #286.
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.
Summary
Curate and date the
## [0.2.4]changelog section ahead of the v0.2.4 release (tracking issue #286).2026-07-02(wasUnreleased).v0.2.3, grouped per Keep a Changelog (Added / Changed / Fixed / Security / Removed / Documentation).Release context
Per the release procedure, the
v0.2.4tag must sit on a commit that already contains the dated changelog. This PR is that commit — once merged, its merge commit becomes the tag target forv0.2.4-rc1(and laterv0.2.4).Refs #286.