Add publish_react_component_library.yaml GitHub Actions workflow file #424
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
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 PR adds a GitHub Actions workflow file that is designed to publish a new version of
@bcgov/design-system-react-componentson npm using thenexttag and with a version that looks like:So package.json version v1.2.3 with a build caused by PR # 456 would result in an npm version of
1.2.3-pr456on thenexttag (not the defaultlatesttag that gives the canonical latest version of the package when a user installs withnpm install).The intent is that we are able to publish and test new versions of the library quickly with less manual action needed.
I have a secret
NPM_TOKENalready added to this repo that this workflow will use. I'm not 100% sure how this will work with npm's MFA requirement that I bump up against every time I manually publish a new version, so we will have to test this if it gets merged.