Skip to content

docs(changelog): finalize v0.1.0 (2026-05-17)#3

Merged
Teerapat-Vatpitak merged 1 commit into
mainfrom
chore/finalize-changelog-v0.1.0
May 17, 2026
Merged

docs(changelog): finalize v0.1.0 (2026-05-17)#3
Teerapat-Vatpitak merged 1 commit into
mainfrom
chore/finalize-changelog-v0.1.0

Conversation

@Teerapat-Vatpitak
Copy link
Copy Markdown
Owner

Summary

  • Finalize the changelog for the v0.1.0 release: rename ## [Unreleased]## [0.1.0] — 2026-05-17, fold the redundant ## [0.1.0] — TBD stub into it, and add a fresh empty ## [Unreleased].
  • Done as a PR (not a direct push to main) per the repo's PRs-only rule; after merge the local v0.1.0 tag is moved to this PR's merge commit and pushed, so the release tag points at a tree whose CHANGELOG reflects the release.

Test plan

  • Docs-only change — no Rust source, API, or behavior touched (CHANGELOG.md only); the full CI matrix (fmt/clippy/build/test/doc/deny on ubuntu/macos/windows + MSRV + audit) runs and passes trivially.
  • CHANGELOG well-formed: exactly one ## [0.1.0] heading, no remaining TBD, compare/release link refs unchanged and still resolve.
  • [Unreleased] is intentionally empty immediately post-release (will be repopulated as v0.2 work lands).

Notes

  • The [Unreleased] / [0.1.0] link reference definitions already pointed at v0.1.0 (compare/v0.1.0...HEAD and releases/tag/v0.1.0) and are unchanged.
  • Follow-up after merge (separate maintainer action, no automation here): v0.1.0 tag → merge commit, git push origin v0.1.0. No cargo publish — the user is intentionally not publishing to crates.io yet.

By contributing you agree your changes are dual-licensed under MIT and Apache-2.0,
matching the project. See CONTRIBUTING.md.

Rename the [Unreleased] section to [0.1.0] — 2026-05-17 so the
v0.1.0 release tag points at a tree whose CHANGELOG reflects the
release (chosen over tagging 333a93c as-is; the tag will be moved
to this PR's merge commit). Folds the redundant '[0.1.0] — TBD'
stub into the dated section and adds a fresh empty [Unreleased];
the compare/release link refs already pointed at v0.1.0 and are
unchanged. Docs-only — no code, API, or behavior change.
@Teerapat-Vatpitak Teerapat-Vatpitak merged commit a3ff6d4 into main May 17, 2026
5 checks passed
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