You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(ci): grant release workflow write permissions - #139
The release branch push still fails with HTTP 403 after #138. The latest run authenticates as swc-bot, and the repository collaborator API reports that account has only read permission (push: false).
Use the repository's GITHUB_TOKEN through the Changesets github-token input, grant contents: write and pull-requests: write, and remove the BOT_GH_TOKEN environment override. Keep persist-credentials: false so Changesets configures Git authentication. Keep the existing OIDC permission for npm publishing.
The repository currently allows GitHub Actions to create pull requests. Release PRs created with GITHUB_TOKEN do not automatically trigger ordinary pull_request workflows.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
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
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.
The release branch push still fails with HTTP 403 after #138. The latest run authenticates as
swc-bot, and the repository collaborator API reports that account has onlyreadpermission (push: false).Use the repository's
GITHUB_TOKENthrough the Changesetsgithub-tokeninput, grantcontents: writeandpull-requests: write, and remove theBOT_GH_TOKENenvironment override. Keeppersist-credentials: falseso Changesets configures Git authentication. Keep the existing OIDC permission for npm publishing.The repository currently allows GitHub Actions to create pull requests. Release PRs created with
GITHUB_TOKENdo not automatically trigger ordinarypull_requestworkflows.Failed run: https://github.com/swc-project/pkgs/actions/runs/40670827614
Validation of the workflow change before commit
6a98e5c:actionlint .github/workflows/publish.ymlpassed.git diff --checkpassed.swc-botcollaborator permissions through the GitHub API.Authenticated release pushes, release PR creation, and npm publishing remain unverified. They require a workflow run with the changed permissions.