Skip to content

release: 2.0.1 — add RELEASING.md#10

Merged
RoyalPineapple merged 3 commits intomainfrom
RoyalPineapple/add-releasing-md
Apr 14, 2026
Merged

release: 2.0.1 — add RELEASING.md#10
RoyalPineapple merged 3 commits intomainfrom
RoyalPineapple/add-releasing-md

Conversation

@RoyalPineapple
Copy link
Copy Markdown
Contributor

@RoyalPineapple RoyalPineapple commented Apr 8, 2026

Adds a RELEASING.md with step-by-step instructions for cutting a release, mirroring Blueprint's process. Release tags target signed merge commits on main, and release notes are auto-generated via GitHub Releases.

Once merged, the signed merge commit will be tagged as 2.0.1.

Checklist

  • Unit Tests
  • Documentation
  • Pull request title follows conventional commits

Add release documentation mirroring Blueprint's format, including a
backfilled changelog and step-by-step releasing guide.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@RoyalPineapple RoyalPineapple marked this pull request as ready for review April 8, 2026 08:50
@RoyalPineapple RoyalPineapple requested a review from a team as a code owner April 8, 2026 08:50
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Comment thread CHANGELOG.md Outdated
Copy link
Copy Markdown
Member

@robmaceachern robmaceachern Apr 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We've been moving away from explicit changelog.md files and just relying on the Github releases to compile the list of relevant changes.

  • Kill changelog.md

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sounds good, i'll kill it

Per review feedback, drop the explicit changelog in favor of GitHub
Releases with auto-generated release notes.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@RoyalPineapple RoyalPineapple changed the title docs: add CHANGELOG.md and RELEASING.md for 2.0.1 docs: add RELEASING.md for 2.0.1 Apr 9, 2026
Copy link
Copy Markdown
Member

@robmaceachern robmaceachern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

  • Update PR description

@RoyalPineapple RoyalPineapple changed the title docs: add RELEASING.md for 2.0.1 docs: add RELEASING.md Apr 14, 2026
@RoyalPineapple RoyalPineapple changed the title docs: add RELEASING.md release: 2.0.1 — add RELEASING.md Apr 14, 2026
@RoyalPineapple RoyalPineapple merged commit 7738543 into main Apr 14, 2026
8 checks passed
@RoyalPineapple RoyalPineapple deleted the RoyalPineapple/add-releasing-md branch April 14, 2026 11:28
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.

2 participants