automate workflow for npm publish #497
Merged
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
Closed
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Thomas-Boi
approved these changes
Feb 21, 2021
GCHQDeveloper926
pushed a commit
to GCHQDeveloper926/devicon
that referenced
this pull request
Dec 20, 2024
* setup npm_publish workflow and update package.json with new repo info * refactoring npm publish workflow to reduce dependencies * npm publish to 2.9.0 * reduce npm publish workflow to publishing task only * npm publish to 2.9.0 * testing npm publish * update npm version to 2.9.0 (latest release) * enhance CONTRIBUTING.md with sentence about npm release workflow
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
I created a workflow which will be triggered when a new release is created. The workflow will try to publish the latest version to
npm.When we want to create a new release, we need to update the
package.jsonandpackage-lock.jsonand set it to the new release version. This can be done via the command (replace v2.9.0 with the new version):This should be done before
developmentis merged intomasterand a new release is created. Otherwise the workflow will fail and throw this exception:When this error occurs you need to checkout the branch, bump the version in the
package.jsonand either publish the package manually or creating a new release to trigger the workflow again.