docs(changelog): cut 0.0.2 (promote Unreleased)#8
Merged
Conversation
- promote the [Unreleased] section to [0.0.2] - 2026-07-05 (en + ko) ahead of tagging so the release commit carries the finalized entry #docs #release Co-Authored-By: htjulia <htjulia1@gmail.com>
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.
Why
Cutting the v0.0.2 release. Per Keep a Changelog, the
[Unreleased]section is promoted to a dated version heading at release time, and this must land onmainbefore thev0.0.2tag so the tagged commit carries the finalized changelog.Change
[Unreleased]→## [0.0.2] - 2026-07-05inCHANGELOG.mdandCHANGELOG.ko.md.v0.0.2 contents = the lua-pure v0.1.2 / Go 1.25 bump (PR #7).
Next (after merge)
Tag
v0.0.2at the merge commit and publish a GitHub pre-release.