Repository navigation
feat(github.release-please): add the composite action for release-please with a GitHub App token - #40
Merged
Merged
Conversation
…ase with a GitHub App token
👋 Welcome! Looks like this is your first pull request.Hey, thanks for your contribution! Please give us a bit of time to review it. 😄 Please check out our contributing guidelines. |
GitHub Actions Integration
✅ All 1 passed. |
This was referenced Oct 11, 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.
👋 Background
Module repositories are adopting release-please (tedilabs/terraform-aws-account#145). Each would repeat the same two steps: create a GitHub App token, so that the release pull requests trigger CI, and run release-please with it. Keeping them in one action keeps the token permissions and action versions in one place.
What changed
github.release-please, a composite action that:actions/create-github-app-token@v3, narrowed tocontents,issues, andpull-requestswrite;googleapis/release-please-action@v5with that token and the manifest config.github_app_client_idandgithub_app_private_key(required),config_fileandmanifest_file(default torelease-please-config.jsonand.release-please-manifest.json).release_created,tag_name, andversionof the root component.Usage:
Notes
secrets, so the App credentials are inputs.action.yml, so only the root component outputs that callers are likely to use are forwarded. Path-prefixed outputs of monorepos (<path>--version) are not forwarded.yamllintandcheck-jsonschema --builtin-schema vendor.github-actionspass.