v3.0.3-rc.0 #60
Open
v3.0.3-rc.0 #60
Conversation
This file contains 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
leoromanovsky
commented
May 16, 2024
| @@ -0,0 +1,30 @@ | |||
| name: Node.js Setup and Test | |||
There was a problem hiding this comment.
Refactor into a shared file so we can be sure the checks are always run.
| uses: ./.github/workflows/nodejs-setup.yml | ||
| with: | ||
| node_version: '18.x' | ||
| npm_tag: rc |
There was a problem hiding this comment.
npm tag goes here; end-users need to explicitly select this tag and it won't "accidentally" be treated as a dependency.
aarsilv
approved these changes
May 20, 2024
| @@ -0,0 +1,30 @@ | |||
| name: Node.js Setup and Test | |||
| @@ -0,0 +1,11 @@ | |||
| name: Publish RC to NPM | |||
| on: | |||
| workflow_dispatch: | |||
There was a problem hiding this comment.
☝️ and this lets us trigger from UI ✅
sameerank
approved these changes
Jun 3, 2024
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.
Fixes: #issue
Motivation and Context
Experimenting with a release process that allows us to have "release candidates" that we can explicitly add to our services and dogfood before publishing for our customers.
Description
Bumping the version programmatically:
To publish this version:
Caveat: this is different than our normal publish command. There is a new github action in this PR that can be executed manually.
For end-users to install:
How has this been tested?