Skip to content

fix(ci): use the GitHub App client ID#8

Merged
m17kea merged 1 commit into
mainfrom
codex/use-github-app-client-id
Jul 16, 2026
Merged

fix(ci): use the GitHub App client ID#8
m17kea merged 1 commit into
mainfrom
codex/use-github-app-client-id

Conversation

@m17kea

@m17kea m17kea commented Jul 16, 2026

Copy link
Copy Markdown

Context

The Node 24 upgrades removed the runtime warnings, but the deployment dispatch still warns that the GitHub App action's app-id input is deprecated.

TL;DR

Use the existing GitHub App client ID through the supported action input.

Summary

  • Replace app-id with client-id when minting the deployment token.
  • Use the new SYMPHONY_DEPLOY_CLIENT_ID repository variable.
  • Update actionlint configuration and the ActiveViam handover documentation.
  • Keep the existing private key and restricted App installation unchanged.

Alternatives

  • Retaining the deprecated compatibility input was rejected because it leaves a warning on every publish.
  • Creating a replacement App was rejected because the existing App already exposes the required client ID.

Test Plan

  • COLUMNS=240 LINES=60 make -C elixir all
  • actionlint -config-file .github/actionlint.yaml
  • Confirmed the configured client ID belongs to ActiveViam Symphony Deployer.

Summary:
- switch the deployment token action to its supported client-id input
- document and lint the new repository variable name

Rationale:
- remove the remaining deprecated app-id input warning
- retain the existing App installation and private-key credential

Tests:
- COLUMNS=240 LINES=60 make -C elixir all
- actionlint -config-file .github/actionlint.yaml

Co-authored-by: Codex <codex@openai.com>
@m17kea
m17kea merged commit 75a80af into main Jul 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant