Skip to content
Open
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ jobs:
steps:
- name: Get auth token
id: token
uses: actions/create-github-app-token@29824e69f54612133e76f7eaac726eef6c875baf # v2
uses: actions/create-github-app-token@1b10c78c7865c340bc4f6099eb2f838309f1e8c3 # v2
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Deprecated app-id input not migrated to client-id

Medium Severity

The action was bumped to v3.1.1 which deprecated the app-id input in favor of client-id, but the workflow still passes the value via app-id. The variable name SENTRY_RELEASE_BOT_CLIENT_ID strongly suggests it holds a Client ID (a string like Iv23li...), which differs in format from a numeric App ID. Passing a Client ID through the deprecated app-id input may trigger validation warnings or failures in v3's stricter identifier handling. The input key here likely needs to be client-id.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 84c7f2d. Configure here.

with:
app-id: ${{ vars.SENTRY_RELEASE_BOT_CLIENT_ID }}
private-key: ${{ secrets.SENTRY_RELEASE_BOT_PRIVATE_KEY }}
Expand Down
Loading