ci: use client-id instead of deprecated app-id for cli releaser github app - #639
Conversation
…token actions/create-github-app-token deprecated the 'app-id' input in favor of 'client-id' (warning: "Input 'app-id' has been deprecated with message: Use 'client-id' instead."). Switch both workflow token steps to 'client-id'. client-id takes the GitHub App's Client ID (string, e.g. Iv23li...), not the numeric App ID that 'app-id' took — so this requires a new repo secret GH_APP_CLIENT_ID_RELEASER (value = the Client ID from the App's settings page). Kept the existing GH_APP_PRIVATE_KEY_RELEASER secret unchanged. Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #639 +/- ##
==========================================
+ Coverage 72.22% 72.25% +0.02%
==========================================
Files 238 238
Lines 20072 20072
==========================================
+ Hits 14497 14503 +6
+ Misses 4302 4300 -2
+ Partials 1273 1269 -4 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Nice cleanup — clears the deprecation warning and the diff is minimal. LGTM on the two workflow files. One follow-up before merge: While you're at it, since you already noted the old |
What
actions/create-github-app-tokendeprecated itsapp-idinput in favor ofclient-id. Every run ofrelease.ymlanddependencies.ymlwas logging:This switches both token steps to
client-id.✅ Secret in place — ready to merge
client-idtakes the App's Client ID (string likeIv23li…), not the numeric App ID thatapp-idtook. The required repo secretGH_APP_CLIENT_ID_RELEASERhas been added (value = the releaser App's Client ID). Both workflow lines reference it.GH_APP_PRIVATE_KEY_RELEASERis unchanged.Files
.github/workflows/release.yml.github/workflows/dependencies.ymlNotes
GH_APP_ID_RELEASERsecret is no longer referenced by any workflow — safe to delete after merge, or leave in place (harmless).app-idstill functioned; this clears the deprecation warning and future-proofs against its eventual removal.🤖 Generated with Claude Code