ci: Add release-please workflow#111
Merged
Merged
Conversation
Adds a release-please workflow modeled on the mozilla/mozcloud setup: push to main opens/updates a Release PR, and merging it tags vX.Y.Z and creates the GitHub Release. The existing build-and-push-to-GAR workflow already triggers on those tags to build the image. - release-type node, single root package, plain vX.Y.Z tags - manifest seeded at the current 0.1.3 tag
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.
Adds a release-please workflow, modeled on the
mozilla/mozcloudsetup.How it works
main→release-please-actionopens/updates a Release PR (version bump + CHANGELOG from conventional commits).vX.Y.Ztag and creates the GitHub Release.v[0-9]+.[0-9]+.[0-9]+tags, so the image build happens automatically off the release tag.Files
.github/workflows/release.yml— release-please job (pinnedgoogleapis/release-please-action@v5.0.0, same SHA as mozcloud). The goreleaser/GCS fanout from mozcloud is Go-tool-specific and intentionally omitted.release-please-config.json—release-type: node, single root package,include-component-in-tag: falseso tags stay plainvX.Y.Z(matching the GAR trigger). Pre-1.0 bump flags keep it on the 0.x line..release-please-manifest.json— seeded at the current0.1.3tag, so only commits sincev0.1.3are considered. First Release PR bumps tov0.1.4.Prerequisite
release-please opens PRs via
GITHUB_TOKEN. This requires Settings → Actions → General → "Allow GitHub Actions to create and approve pull requests" to be enabled (as on mozcloud); otherwise the action needs a PAT.Note
With
release-type: node, the first release reconciles rootpackage.json(currently drifted at1.0.0) down to the real version line (0.1.x).