feat: add automatic release changelog with release-please#21
Merged
Conversation
blimmer
commented
May 6, 2026
| @@ -0,0 +1,37 @@ | |||
| name: Lint PR title | |||
Contributor
Author
There was a problem hiding this comment.
I will add this to the required checks once merged. It ensures that people follow conventional-commit so our changelog works.
| contents: write | ||
| pull-requests: write | ||
| steps: | ||
| - name: Generate ContextBridge app token |
Contributor
Author
There was a problem hiding this comment.
Needs to be able to write to the repo, so using our app
Comment on lines
+15
to
+21
| { "type": "docs", "section": "Documentation", "hidden": true }, | ||
| { "type": "chore", "section": "Miscellaneous", "hidden": true }, | ||
| { "type": "style", "section": "Styles", "hidden": true }, | ||
| { "type": "refactor", "section": "Refactors", "hidden": true }, | ||
| { "type": "test", "section": "Tests", "hidden": true }, | ||
| { "type": "build", "section": "Build", "hidden": true }, | ||
| { "type": "ci", "section": "CI", "hidden": true } |
Contributor
Author
There was a problem hiding this comment.
Thoughts on hidden sections? Does this seem like a good starting place?
Contributor
There was a problem hiding this comment.
Yea think this looks like a good starting point in that we want user-facing changes visible but refactoring etc not.
blimmer
force-pushed
the
17-automatic-release-changelog
branch
from
577186f to
3d07f37
Compare
jcarver989
approved these changes
May 6, 2026
Contributor
jcarver989
left a comment
jcarver989
left a comment
There was a problem hiding this comment.
Looks reasonable, thanks!
Comment on lines
+15
to
+21
| { "type": "docs", "section": "Documentation", "hidden": true }, | ||
| { "type": "chore", "section": "Miscellaneous", "hidden": true }, | ||
| { "type": "style", "section": "Styles", "hidden": true }, | ||
| { "type": "refactor", "section": "Refactors", "hidden": true }, | ||
| { "type": "test", "section": "Tests", "hidden": true }, | ||
| { "type": "build", "section": "Build", "hidden": true }, | ||
| { "type": "ci", "section": "CI", "hidden": true } |
Contributor
There was a problem hiding this comment.
Yea think this looks like a good starting point in that we want user-facing changes visible but refactoring etc not.
This was referenced May 6, 2026
blimmer
added a commit
that referenced
this pull request
May 8, 2026
🤖 I have created a release *beep* *boop* --- ## [0.3.0](v0.2.0...v0.3.0) (2026-05-08) ### ⚠ BREAKING CHANGES * rename Claude plugin to planbridge@contextbridge; refresh plugins on update ([#52](#52)) ### Features * add automatic release changelog with release-please ([#21](#21)) ([45a1bf1](45a1bf1)) * rename Claude plugin to planbridge@contextbridge; refresh plugins on update ([#52](#52)) ([2794ae6](2794ae6)) * **ui:** add GitHub link to header help menu ([#19](#19)) ([c36289b](c36289b)) ### Bug Fixes * emit plan review analytics from shared runner ([#48](#48)) ([5c769ff](5c769ff)) * **plan:** pre-scan src for transitive deps to stop vitest reload flake ([3b3cc0c](3b3cc0c)), closes [#12](#12) * **plan:** stop vitest reload flake from lazy zod optimization ([#15](#15)) ([3b3cc0c](3b3cc0c)) * refresh Claude marketplace cache during install ([#62](#62)) ([58be09a](58be09a)) * resolve contextbridge via PATH for post-update refresh ([#64](#64)) ([f658af4](f658af4)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: contextbridge-pr-automation[bot] <259134118+contextbridge-pr-automation[bot]@users.noreply.github.com> Co-authored-by: Ben Limmer <ben@benlimmer.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
2 participants
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.
Closes #17.
Summary
Adds release-please as the source of truth for stable-release versioning and
CHANGELOG.md, while keeping the existing goreleaser pipeline as the artifact-distribution layer. release-please opens a Release PR on each push tomain; merging it creates the tag and a GitHub Release whose body is the new CHANGELOG entry. Goreleaser then runs on the tag push withrelease.mode: keep-existing, attaching tarballs and casks without disturbing the body. Manual alpha tags continue to bypass release-please entirely. The CLI's update prompts and the plan UI's update card now link to the per-version GitHub Release page so users can see what changed before upgrading.Review focus
release.mode: keep-existing(.goreleaser.yaml). Without it, goreleaser would clobber release-please's curated body. Worth eyeballing the order of operations described inrelease-please-config.json+release-please.ymlagainst the existing tag-triggeredrelease.yml.release-type: gofor a TypeScript repo. The label is misleading but the behavior fits: it bumpsCHANGELOG.mdonly, not any version file. We don't want package.json drifting from0.0.0-developmentsince goreleaser injects the real version from the tag.0.2.0. Pinning matches the most recent stable tag so the first release-please run computes fromv0.2.0forward, not from repo inception.amannn/action-semantic-pull-request,googleapis/release-please-action,actions/create-github-app-token) are SHA-pinned with the version as a trailing comment. Matches existing pattern inrelease.yml.release-please.yml. SameCB_PR_AUTOMATION_APP_*pair already used byrelease.yml. Required so the tag release-please pushes triggers downstream workflows — a defaultGITHUB_TOKENwould not.UpdateNoticeCardlink placement. First pass put a "What's new" link mid-description, which wrapped awkwardly in the 20rem card. Final design makesv{version}in the title itself the link — same compact 3-line layout as before.Commits
5e29026— feat: add automatic release changelog with release-please5ee1908— refactor: use sharedGITHUB_REPO_URLfor release links3d07f37— docs: document release process in CONTRIBUTING