Repository navigation
Migrate releases to release-please - #44
Merged
Merged
Conversation
Adds release-please (googleapis/release-please-action v5) to own the version bump, tag, and GitHub release. The publish workflow gains a workflow_dispatch trigger and is kicked off automatically when release-please cuts a release (GITHUB_TOKEN-created tags don't fire push/tags triggers). The draft-publishing 'release' job and release-drafter are removed; release notes now come from the release-please release itself. Co-Authored-By: Quentin Rousseau <quentin@rootly.com>
Contributor
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
Adds a release job gated on push events that creates the GitHub release when none exists (manual v* tag pushes). The release-please dispatch path is unaffected — this job only runs on push, and the release already exists there. Replaces the removed draft-publish tail job. Co-Authored-By: Quentin Rousseau <quentin@rootly.com>
Co-Authored-By: Quentin Rousseau <quentin@rootly.com>
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Self-review pass (Devin):
- Manifest
3.0.1matches latest remote tagv3.0.1; trigger onmaster; config + workflow YAML parse clean. release-please.ymldispatchespublish.ymlwithactions: write; manualv*tag push still runs the full publish.- Added
releasejob (push-only) so manual tags still get a GitHub release — the deleted draft-publish tail used to do this.contents: writescoped to that job only. - CI: green except
test (3.11)still running.
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.
Summary
Moves releases to release-please, matching rootly-desktop / rootly-mcp-server / rootly-go. Replaces release-drafter + manual tagging: a release PR opens on pushes to
master, and merging it cuts the tag, GitHub release, and dispatch topublish.yml(a GITHUB_TOKEN-created tag does not firepush: tags, hence the dispatch).release-please-config.json+.release-please-manifest.json(seeded at 3.0.1)release-please.ymlrunsgoogleapis/release-please-actionv5, thengh workflow run publish.yml --ref $TAGpublish.ymlgainsworkflow_dispatch; the draft-release tail job is deleted (the release already exists when it runs)release-drafter.yml+.github/release-drafter.ymldeletedManual
v*tag pushes still run publish as before. Rollback = revert this PR.Link to Devin session: https://rootly.devinenterprise.com/sessions/774103253f13428589402ae6862eeaeb
Open in Devin Desktop: https://rootly.devinenterprise.com/desktop/session/774103253f13428589402ae6862eeaeb?variant=devin
Requested by: @kwent