Context
actions/create-github-app-token@v3.2.0 accepts the legacy app-id input but emits a deprecation warning and recommends client-id instead. The LibreSign end-to-end Update workflows run exposed this warning.
GitHub's current documentation treats the Client ID as a distinct GitHub App configuration value. We must not simply rename the existing numeric App ID variable and pass it as client-id.
Migration
Add the real GitHub App Client ID values as repository/organization variables:
LIBRECODE_WORKFLOW_APP_CLIENT_ID for the shared LibreCode Workflow Automation app;WORKFLOW_SYNC_APP_CLIENT_ID for the optional consumer-specific GitHub App mode.
Then update workflow-templates/sync-workflow-templates.yml and upstream-refresh.yml to use client-id: and update validation/documentation accordingly. Remove the old *_APP_ID variables only after all consumers have materialized the new workflow and successful end-to-end runs confirm the migration.
Why this is separate
The current app-id path still works and is not the cause of the failed sync. Changing it without first provisioning the correct Client ID would turn a warning into an authentication outage.
Context
actions/create-github-app-token@v3.2.0accepts the legacyapp-idinput but emits a deprecation warning and recommendsclient-idinstead. The LibreSign end-to-endUpdate workflowsrun exposed this warning.GitHub's current documentation treats the Client ID as a distinct GitHub App configuration value. We must not simply rename the existing numeric App ID variable and pass it as
client-id.Migration
Add the real GitHub App Client ID values as repository/organization variables:
LIBRECODE_WORKFLOW_APP_CLIENT_IDfor the shared LibreCode Workflow Automation app;WORKFLOW_SYNC_APP_CLIENT_IDfor the optional consumer-specific GitHub App mode.Then update
workflow-templates/sync-workflow-templates.ymlandupstream-refresh.ymlto useclient-id:and update validation/documentation accordingly. Remove the old*_APP_IDvariables only after all consumers have materialized the new workflow and successful end-to-end runs confirm the migration.Why this is separate
The current
app-idpath still works and is not the cause of the failed sync. Changing it without first provisioning the correct Client ID would turn a warning into an authentication outage.