ci: add GitHub Actions verification and npm release automation#5
Merged
Conversation
Owner
Author
|
I pushed a follow-up fix to this branch. The failing CI root cause was that the workflows called |
Owner
Author
|
Merged after fixing the CI regression. The failing checks were caused by the workflows calling |
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
CIworkflow that runs build, tests, release guards,npm pack, and isolated install/doctor smoke checks on PRs andmainReleaseworkflow that reacts tov*.*.*tag pushes, re-runs verification, publishes to npm with provenance via trusted publishing, and creates the matching GitHub Releaserelease.ymlso it can be wired to npm trusted publishing withnpm trust githubWhy
This lets future releases publish from GitHub Actions without needing npm auth on a local machine, while still guarding the package with the same checks we run manually.
One-time npm setup after merge
Future release flow
git push origin main --follow-tags.