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.
Refer https://github.com/marketplace/actions/publish-to-npm. Adding their instruction to this PR to make it easier for you.
When someone changes the version in
package.json
to 1.2.3 and pushes a commit to master with the messageRelease 1.2.3
, thenpm-publish
action will create a new tagv1.2.3
and publish the package to the npm registry.Inputs
These inputs are optional: that means that if you don't enter them, default values will be used and it'll work just fine.
tag_name
: the name pattern of the new tagtag_message
: the message pattern of the new tagcommit_pattern
: the pattern that the commit message needs to followworkspace
: custom workspace directory that contains the package.json fileEnvironment variables
GITHUB_TOKEN
: this is a token that GitHub generates automatically, you only need to pass it to the action as in the exampleNPM_AUTH_TOKEN
: this is the token the action will use to authenticate to npm. You need to generate one in npm, then you can add it to your secrets (settings -> secrets) so that it can be passed to the action. DO NOT put the token directly in your workflow file.