Skip to content

upgrade: update actions/create-github-app-token action to v3 #468

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

upgrade: update actions/create-github-app-token action to v3 #468

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ jobs:
runs-on: ubuntu-latest
steps:
- id: app-token
uses: actions/create-github-app-token@29824e69f54612133e76f7eaac726eef6c875baf # v2.2.1
uses: actions/create-github-app-token@f8d387b68d61c58ab83c6c016672934102569859 # v3.0.0
with:
app-id: ${{ secrets.APP_ID }}
private-key: ${{ secrets.APP_PRIVATE_KEY }}
Comment on lines +17 to 20
Copy link
Copy Markdown

@devin-ai-integration devin-ai-integration bot Apr 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚩 Major version bump may require input parameter name changes

The action is bumped from v2.2.1 to v3.0.0 — a major version change that typically signals breaking API changes. The workflow currently uses app-id and private-key (hyphenated) as input names (.github/workflows/release.yml:19-20). Major versions of actions/create-github-app-token have historically changed input naming conventions (e.g., from hyphenated to underscored). I could not verify the v3 input API from repository context alone, so this is not flagged as a bug, but it warrants investigation to ensure app-id and private-key are still valid input names in v3.0.0. If they were renamed to app_id and private_key, the workflow would silently fail to pass the required credentials.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Expand Down
Loading