ci: automate checks merges and releases - #1
Merged
Merged
Conversation
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.
Summary
main.Security
pull_request_targetworkflow only calls the GitHub API and never checks out PR code.id-token: write) with no npm token secret.NPM_TRUSTED_PUBLISHING_ENABLED=true.mainrequires pull requests and theBun check; force pushes and deletion are blocked.Verification
actionlintbun run check— 21 files, 233 testsnpm pack --dry-runBootstrap
This first PR must have auto-merge enabled manually because
pull_request_targetloads workflow code from the default branch. After merge,the npm trusted publisher and release gate variable will be configured, then a
second owner PR will prove the complete automatic merge and release chain.