Skip to content

chore(release): 0.3.0#119

Merged
ThomasK33 merged 1 commit into
mainfrom
release/0.3.0
Jun 3, 2026
Merged

chore(release): 0.3.0#119
ThomasK33 merged 1 commit into
mainfrom
release/0.3.0

Conversation

@ThomasK33
Copy link
Copy Markdown
Member

Release prep for v0.3.0 (first 0.3.x cut on top of v0.2.0).

What's in this PR

  • Bumps package.json version 0.2.00.3.0.
  • Renames the curated ## [Unreleased] changelog section to ## [v0.3.0] - 2026-06-03 and inserts a fresh empty ## [Unreleased] heading above it (per docs/RELEASE-PROCESS.md, this keeps both headings on main so Release Changelog skips its Communique pass and Update Unreleased Changelog keeps working post-merge). Sub-headings normalized to ### to match every prior released section.

Headline changes since v0.2.0

Release mechanics

After this merges, the release is finalized by tagging v0.3.0 from synced main (npm run release:finalize), which triggers the Release workflow to publish the GitHub Release and npm package.

🤖 Generated with Claude Code

Change-Id: If831f7a10280b680866b0e39f64f6634231d8d0e
Signed-off-by: Thomas Kosiewski <tk@coder.com>
@ThomasK33 ThomasK33 merged commit a05d4e5 into main Jun 3, 2026
13 checks passed
@ThomasK33 ThomasK33 deleted the release/0.3.0 branch June 3, 2026 18:15
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