docs(changelog): finalize dated v0.3.0 section - #39
Merged
Conversation
The v0.3.0 tag was pushed by GITHUB_TOKEN (tag.yaml), which does not trigger the changelog release workflow, so the dated section is regenerated and landed manually (as v0.2.2 was). Rolls [Unreleased] into [0.3.0] - 2026-07-31.
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Finalizes the changelog for the v0.3.0 release. The tag was created by
tag.yaml(GITHUB_TOKEN), which does not trigger the changelog release job, so the dated[0.3.0] - 2026-07-31section is regenerated and landed manually — the same manual path used for v0.2.2.