Setting up GitHub CI for packages #2365
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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 introduces two new GitHub Actions workflows to automate the release process for Node.js packages. One workflow handles production releases for the
mainbranch, while the other manages staging (alpha) releases for thedevelopbranch. These workflows streamline the build, test, and publish processes for multiple packages with specific Node.js versions.New GitHub Actions Workflows
Production Workflow:
.github/workflows/node-production.ymlto handle production releases triggered by pushes to themainbranch. The workflow builds and publishes packages to npm with thelatesttag, skipping alpha versions.Staging Workflow:
.github/workflows/node-staging.ymlto handle staging releases triggered by pushes to thedevelopbranch. The workflow builds and publishes alpha versions of packages to npm with thenexttag, skipping non-alpha versions.