Skip to content

ci: use new gh app for pr bypass when publishing#2412

Merged
jakehobbs merged 1 commit intomainfrom
jake/use-default-token-for-publishing
Mar 23, 2026
Merged

ci: use new gh app for pr bypass when publishing#2412
jakehobbs merged 1 commit intomainfrom
jake/use-default-token-for-publishing

Conversation

@jakehobbs
Copy link
Collaborator

@jakehobbs jakehobbs commented Mar 20, 2026


PR-Codex overview

This PR updates the .github/workflows/publish-package.yml workflow to generate a GitHub app token dynamically instead of using a static personal access token. This enhances security by leveraging GitHub's app authentication.

Detailed summary

  • Added a step to generate an app token using actions/create-github-app-token@v1.
  • Set the app-id and private-key using secrets.
  • Replaced the static token with the generated token from the app token step in the checkout process.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Co-Authored-By: Claude <noreply@anthropic.com>
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the package publishing workflow to use a dynamically generated GitHub App installation token instead of a long-lived personal access token, improving credential security for repository writes during publish.

Changes:

  • Added a step to generate a GitHub App token via actions/create-github-app-token@v1.
  • Switched actions/checkout authentication to use the generated app token output.

@jakehobbs jakehobbs merged commit a79fbfe into main Mar 23, 2026
14 checks passed
@jakehobbs jakehobbs deleted the jake/use-default-token-for-publishing branch March 23, 2026 19:10
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.

3 participants