Repository navigation
chore: move to release-please for release management - #260
Merged
Merged
Conversation
Replace the hand-written "prepare X.Y.Z release" PRs with release-please, driven by Conventional Commit PR titles, matching ld-find-code-refs. Merging the release PR now creates a draft release and the vX.Y.Z tag, builds and pushes the Docker Hub image, publishes the release and moves v2. publish.yml replaces publish-image.yml (tags pushed with GITHUB_TOKEN never triggered it) and is shared with manual-publish.yml for dry runs and recovery. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Generated-by: termag
cspath1
commented
Oct 23, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Generated-by: termag
cspath1
force-pushed
the
release-please
branch
from
October 23, 2026 14:09
3659f4f to
b55b604
Compare
Contributor
Author
|
@BugBot review |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit b55b604. Configure here.
Manual Publish with publish_release on an older tag would mark it the latest release, push it as the latest image and move v2 back to it. Check whether the tag is the newest vMAJOR.x.y and skip all three if not. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Generated-by: termag
cchu-ld
approved these changes
Oct 23, 2026
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
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.
Replace the hand-written "prepare X.Y.Z release" PRs with release-please, driven by Conventional Commit PR titles, matching ld-find-code-refs.
Merging the release PR now creates a draft release and the vX.Y.Z tag, builds and pushes the Docker Hub image, publishes the release and moves v2. publish.yml replaces publish-image.yml (tags pushed with GITHUB_TOKEN never triggered it) and is shared with manual-publish.yml for dry runs and recovery.
Generated-by: termag
Note
Overview
Replaces manual prepare X.Y.Z release PRs with release-please, aligned with ld-find-code-refs. Conventional Commit PR titles are enforced via a new
lint-pr-title.ymlworkflow; changelog and version bumps come from merged PR titles instead of hand-editing[Unreleased].Release automation:
release-please.ymlon pushes tomainopens/updates the release PR, creates draft releases andvX.Y.Ztags, dispatchesmain.ymlso CI runs on release PRs (token-created PRs do not firepull_request), then calls sharedpublish.ymlto build/push Docker Hub images, publish the GitHub release, and movev2only after the image exists.publish-image.ymlis removed (tag pushes fromGITHUB_TOKENdid not trigger it).manual-publish.ymlreusespublish.ymlfor dry-run builds and failed-release recovery, with guards so republishing an older tag does not movelatestor the major tag backward.Docs (
AGENTS.md,DEVELOPMENT.md,CHANGELOG.md) andx-release-please-versionmarkers onversion.go,docker/action.yml, and README reflect the new flow.Reviewed by Cursor Bugbot for commit 551e1e9. Bugbot is set up for automated code reviews on this repo. Configure here.