Skip to content

chore(POP-1693): rename App credentials to the po- prefix - #399

Merged
vitalii-vanziak-cko merged 1 commit into
masterfrom
chore/POP-1693-po-prefix
Sep 1, 2026
Merged

chore(POP-1693): rename App credentials to the po- prefix#399
vitalii-vanziak-cko merged 1 commit into
masterfrom
chore/POP-1693-po-prefix

Conversation

@nestor-colt-cko

Copy link
Copy Markdown
Contributor

Renames the GitHub App credentials in the release workflows from the CKO_ prefix to PO_, following the org naming-convention change.

vars.CKO_PUBLIC_WRITE_APP_IDvars.PO_PUBLIC_WRITE_APP_ID
secrets.CKO_PUBLIC_WRITE_APP_KEYsecrets.PO_PUBLIC_WRITE_APP_KEY

Nothing else changes. App ID 4739572 and installation 157024212 are unchanged — a GitHub App rename moves only the slug and the credential names, not the identity, so the token these workflows mint is the same one.

Merge order matters. These are live release paths. Merge only after PO_PUBLIC_WRITE_APP_ID and PO_PUBLIC_WRITE_APP_KEY are published as org variable/secret scoped Selected repositories for processout-android and processout-ios, and before the CKO_ ones are deleted. Both names can coexist during the switch.

Verification is the next release dispatch authenticating on the new names — these workflows are workflow_dispatch-only, so normal PR CI does not exercise them.

Related: POP-1693, processout/actions#455.

By Nestor Colt - Platform Engineering

The org GitHub App naming convention moves from cko- to po-, so the release
workflows read PO_PUBLIC_WRITE_APP_ID and PO_PUBLIC_WRITE_APP_KEY instead of
the CKO_ ones.

App ID 4739572 and installation 157024212 are unchanged; a rename moves only
the slug and the credential names. Merge after the PO_ org variable and secret
are published for these two repos, and before the CKO_ ones are deleted.
@vitalii-vanziak-cko
vitalii-vanziak-cko merged commit d01c6c7 into master Sep 1, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants