Skip to content

Authenticate the coverage publish job with the app's client ID - #123

Merged
Denis-Averin merged 1 commit into
mainfrom
coverage-app-client-id
Nov 10, 2026
Merged

Denis-Averin merged 1 commit into
mainfrom
coverage-app-client-id

Conversation

@Denis-Averin

@Denis-Averin Denis-Averin commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

actions/create-github-app-token@v3 deprecates the app-id input ("Input 'app-id' has been deprecated with message: Use 'client-id' instead." in the Publish coverage job). This switches the publish-coverage job to the GitHub App's client ID:

-    if: ... && vars.COVERAGE_APP_ID != ''
+    if: ... && vars.COVERAGE_APP_CLIENT_ID != ''
 ...
-          app-id: ${{ vars.COVERAGE_APP_ID }}
+          client-id: ${{ vars.COVERAGE_APP_CLIENT_ID }}

The private key secret COVERAGE_APP_PRIVATE_KEY stays the same.

Before merging

Create the organization variable COVERAGE_APP_CLIENT_ID with the Client ID of the aspose-barcode-cloud-coverage app (app settings → General → About, Iv23li…), with access for the 8 SDK repositories. Merging earlier is safe: until the variable exists the publish job is skipped, not failed, so the coverage badge just stays at its last value.

Once all 8 SDKs use COVERAGE_APP_CLIENT_ID, the old variable COVERAGE_APP_ID can be deleted.

Same change in all SDKs and the codegen docs:


Generated by Claude Code

actions/create-github-app-token@v3 deprecates the app-id input in favour of
client-id. The publish-coverage job now reads the GitHub App's client ID
from the organization variable COVERAGE_APP_CLIENT_ID and is skipped until
that variable exists.
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