Integrate Version Checking into Existing Test Workflow and Automate NPM Publishing on Tag Push #396
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 enhances our existing CI process by integrating version checking into the 'Test' workflow that runs on every push, and automating NPM publishing when a tag is pushed.
Version Checking: As part of the existing 'Test' workflow, a new step has been added. If there are any changes between the current commit and the last tagged version, this step checks to see if the version in package.json is updated.
NPM Publishing: Automatically publishes the package to NPM when a tag is pushed.