fix: trying release with an app - #6
Merged
Merged
Conversation
Remove @semantic-release/git plugin so version bumps aren't committed back to main, eliminating the need for branch protection bypass. Tags and releases are still created normally.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Move verifyConditionsCmd and prepareCmd to @semantic-release/exec plugin where they belong, and remove duplicate @semantic-release/github declaration.
Replace PAT with GitHub App authentication using actions/create-github-app-token. This allows the fostersquirrel-release-bot app to bypass branch protection while keeping manual pushes protected.
MichielDean
enabled auto-merge (squash)
October 26, 2025 17:55
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR updates the GitHub release workflow to use GitHub App authentication instead of the default GITHUB_TOKEN, enabling elevated permissions for the semantic release process.
Key changes:
- Replaced
GITHUB_TOKENwith GitHub App token for authenticated operations - Added documentation for the automated pull request workflow process
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.github/workflows/release.yml |
Integrates GitHub App token generation for authentication in the release workflow |
.github/instructions/copilot.instructions.md |
Removes redundant integration characteristic and adds PR workflow guidelines |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
fostersquirrel-release-bot Bot
pushed a commit
that referenced
this pull request
Oct 26, 2025
## 1.0.0 (2025-10-26) ### 🐛 Bug Fixes * **ci:** use absolute paths for release script checksum steps ([#4](#4)) ([4043558](4043558)) * more release fixes... ([#3](#3)) ([6fc18d6](6fc18d6)) * node version for release ([#2](#2)) ([6a4cf90](6a4cf90)) * specific permissions to bypass the release ([#5](#5)) ([312aa4f](312aa4f)) * trying release with an app ([#6](#6)) ([61866be](61866be))
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
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.
This pull request updates the authentication method used in the release workflow to improve security and align with GitHub best practices. Instead of using a personal access token, the workflow now generates a GitHub App token for all authentication steps.
Authentication improvements:
actions/create-github-app-token@v1action, replacing the previous use of a personal access token for authentication in the release workflow (.github/workflows/release.yml).Checkout repositoryandRun semantic-releasesteps to use the newly generated GitHub App token instead of the personal access token (.github/workflows/release.yml). [1] [2]