DEV: Prepare the 0.3.0 release#65
Merged
Merged
Conversation
Documents the release flow (version bump + bundle install + one commit; CI publishes the gem, tags, and creates the GitHub release with bin/generate-release-notes) so the next release doesn't need archaeology. Also states the ground rules: merging PRs is never part of releasing, and nothing gets pushed to main without approval.
Performance work was invisible in release notes because it carried DEV: prefixes — but a 2x parser speedup is user-facing for a gem. PERF: commits (and squash-body bullets) now land in their own "⚡ Performance" section, after Features and Bug Fixes.
The AST::Quote field renames (post/topic → post_number/topic_id, plus new post_id/user_id, all Integer), the TextFormatter attribution change for id-based quotes, the bare/relative URL rendering changes, and the new String-only tag contract with render_default as the fall-through. Also pins the pre-existing "0.x" heading of the migration-API redesign section to 0.2.0 — the release that actually shipped it (placeholder from before the version was decided).
gschlager
force-pushed
the
prepare-0-3-0-release
branch
from
7a188fe to
45ed3d0
Compare
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.
Everything the 0.3.0 release needs except the version bump itself (that stays a single
DEV: Bump version to 0.3.0commit on main once this is in)..claude/skills/release/SKILL.md) — documents the flow: bumplib/markbridge/version.rb,bundle installfor the lockfile, one two-file commit, push to main; CI publishes the gem, tags, and creates the GitHub release frombin/generate-release-notes. Also states that merging PRs is never part of releasing.AST::Quotefield renames and Integer typing, the TextFormatter attribution change for id-based quotes, the bare/relative URL rendering changes, and the String-only tag contract withinterface.render_defaultas the fall-through.Release-notes preview for 0.3.0 with this merged: 3 Features + 1 Fix (#62) and 9 Performance entries (#58–#61).