ci: Migrate from the defunct release-please app to release-please-action - #27
Merged
Conversation
The release-please GitHub App was turned down by Google on 2025-08-14 (googleapis/release-please#2569), so the .github/release-please.yml app config no longer does anything and no release PRs get opened. Replace it with a release-please workflow using googleapis/release-please-action@v4, which reads the existing release-please-config.json and .release-please-manifest.json unchanged. Because tags created with the workflow GITHUB_TOKEN cannot trigger the tag-based gem-push workflow, the gem publish steps run as a second job in the same workflow, gated on a release having been created.
Pin all actions to commit SHAs, disable git credential persistence on checkouts, add read-only default permissions to test and pr-title workflows, and stop using the bundler cache in the gem publishing jobs (cache poisoning hardening, matching ruby-jwt's push_gem.yml).
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.
Why
The release-please GitHub App was turned down by Google on 2025-08-14 (googleapis/release-please#2569). The
.github/release-please.ymlapp config has been dead since then — no release PR was opened for the releasable commits currently onmain, and none ever will be.What
.github/release-please.ymlapp config..github/workflows/release-please.ymlusinggoogleapis/release-please-action@v5, which reads the existingrelease-please-config.jsonand.release-please-manifest.jsonunchanged. On every push tomainit opens/updates the release PR; when the release PR is merged it creates the tag and GitHub release.gem-push.yml), gated onrelease_created. This is needed because tags created with the workflow'sGITHUB_TOKENcannot trigger the tag-basedgem-push.ymlworkflow (GitHub anti-recursion rule).gem-push.ymlis left in place as a fallback for manually pushed tags.persist-credentials: falseon checkout;zizmorreports no findings.Action required before the first release
The RubyGems OIDC role (
rg_oidc_akr_d5dztzq4ywp3y7rd7vfp) may be scoped to thegem-push.ymlworkflow. If so, update the role on rubygems.org to also permit.github/workflows/release-please.ymlbefore merging the first release PR, or the publish job will fail credential exchange.🤖 Generated with Claude Code