ci: switch release bot token generation to client-id#32
Merged
Conversation
The publish job has been failing with "A JSON web token could not be decoded" since the `BOT_APP_ID` secret value was swapped to the App's Client ID (Iv23li…). `actions/create-github-app-token@v3`'s `app-id` input is deprecated and only accepts numeric App IDs, so a Client ID passed as `app-id` produces an invalid JWT issuer claim. Switch to the `client-id` input to match the secret's current value. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
This was referenced May 14, 2026
kulesy
added a commit
to tinacms/upstash-redis-level
that referenced
this pull request
May 14, 2026
## Summary - The push-to-main publish job has been failing with `A JSON web token could not be decoded` ([run](https://github.com/tinacms/upstash-redis-level/actions/runs/25705443854)) since the `BOT_APP_ID` secret value was swapped to the App's Client ID (`Iv23li…`). - `actions/create-github-app-token@v3`'s `app-id` input is deprecated and only accepts numeric App IDs; passing a Client ID through it yields an invalid JWT issuer claim, which is what the error reports. - Switching to `client-id` matches the secret's current value and unblocks the changeset-driven release of the post-ESM-migration version. Same fix as [tinacms/sqlite-level#32](tinacms/sqlite-level#32). ## Test plan - [ ] On merge, watch the publish job — the "Generate a token" step should succeed. - [ ] Confirm changesets/action either opens a "Version Packages" PR or publishes a beta snapshot. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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
2 participants
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.
Summary
A JSON web token could not be decoded(run) since theBOT_APP_IDsecret value was swapped to the App's Client ID (Iv23li…).actions/create-github-app-token@v3'sapp-idinput is deprecated and only accepts numeric App IDs; passing a Client ID through it yields an invalid JWT issuer claim, which is what the error reports.client-idmatches the secret's current value and unblocks the changeset-driven release ofsqlite-level@2.0.0(thefeat: remove cjs support, move to esmchangeset queued by #24).Test plan
sqlite-level@2.0.0should publish to npm.🤖 Generated with Claude Code