ci: use GitHub App token for release bump PR#438
Merged
ruromero merged 1 commit intoguacsec:mainfrom Apr 27, 2026
Merged
Conversation
Contributor
Reviewer's guide (collapsed on small PRs)Reviewer's GuideConfigures the release workflow to generate a GitHub App-based token and use it for the post-release bump pull request so that CI is triggered on the created PR. Sequence diagram for release bump PR using GitHub App tokensequenceDiagram
actor Developer
participant ReleaseWorkflow as Release_workflow_release_yml
participant GitHubApp as CI_GitHub_App
participant GitHubAPI as GitHub_API
participant BumpPR as Bump_Version_PR
participant BuildWorkflow as Build_and_test_Java_21_workflow
Developer->>ReleaseWorkflow: Trigger workflow_dispatch release
ReleaseWorkflow->>ReleaseWorkflow: Run Maven release steps
ReleaseWorkflow->>GitHubAPI: Request GitHub App token
GitHubAPI-->>ReleaseWorkflow: Return installation access token
ReleaseWorkflow->>GitHubApp: Use token with create_pull_request action
GitHubApp->>GitHubAPI: Create bump version PR
GitHubAPI-->>BumpPR: Open PR authored by GitHub App identity
GitHubAPI->>BuildWorkflow: Trigger Build and test Java 21 on PR events
BuildWorkflow-->>GitHubAPI: Report CI status on bump PR
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Contributor
There was a problem hiding this comment.
Hey - I've left some high level feedback:
- Consider adding a conditional or fallback path for forks or environments where
CI_APP_ID/CI_APP_PRIVATE_KEYare not configured so the release workflow fails more gracefully instead of at the token-generation step. - Double-check that the GitHub App used here has the minimum required repo and workflow permissions for
peter-evans/create-pull-requestto operate, and document or enforce those permissions to avoid future permission-related failures.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Consider adding a conditional or fallback path for forks or environments where `CI_APP_ID` / `CI_APP_PRIVATE_KEY` are not configured so the release workflow fails more gracefully instead of at the token-generation step.
- Double-check that the GitHub App used here has the minimum required repo and workflow permissions for `peter-evans/create-pull-request` to operate, and document or enforce those permissions to avoid future permission-related failures.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Strum355
approved these changes
Apr 24, 2026
The post-release version bump PR created by github-actions[bot] using GITHUB_TOKEN does not trigger CI checks (GitHub's anti-recursion rule). Use a GitHub App token instead so the PR triggers the Build workflow. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
9ccd9e3 to
ee0f9dc
Compare
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
github-actions[bot]usingGITHUB_TOKENdon't trigger CI checks (GitHub's anti-recursion protection)actions/create-github-app-token@v2with the installed GitHub App (CI_APP_ID/CI_APP_PRIVATE_KEYsecrets) to generate a tokenpeter-evans/create-pull-request@v8so the resulting PR triggers the "Build and test Java 21" workflowTest plan
workflow_dispatchand verify the bump PR triggers the Build checkgithub-actions[bot]🤖 Generated with Claude Code
Summary by Sourcery
CI: