ci: pass client-id instead of the legacy app-id - #41
Merged
Conversation
actions/create-github-app-token recommends client-id over the legacy app-id input, and its runtime warns on app-id. Nothing is broken and no removal has been announced, so this is hardening rather than a repair. The 1Password reference moves to the matching 'client id' field on the same item, still addressed by item UUID rather than title. Closes #40
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
What changed and why
actions/create-github-app-tokenis being passed the legacyapp-idinput. Its README recommendsclient-id, and its runtime emits a warning namingapp-idas deprecated. Nothing is broken and no removal has been announced, so this is hardening rather than a repair.Two lines: the action now receives
client-id, and the 1Password reference points at the matchingclient idfield on the same item. The reference stays addressed by item UUID rather than title, so renaming the item cannot break it.Closes #40
How it was verified
op readresolvesop://Automation/lnacky4l2tmlihrockbutkub7y/client id(20 characters,Iv23li…prefix, the documented GitHub App client ID shape).op readstill resolves.../private key, which this change does not touch.app idop reference and exactly one matchingapp-id:input, and asserts afterwards that noapp-id:remains, that there is exactly one/client id, and exactly one/private key. It refuses to touch a file that does not match that shape.Part of a 15-repository sweep. The identical change was landed and proven on
rubicon/daxdavis-comfirst rather than rolled out everywhere on an assumption.Checklist
dev/<issue>-<slug>