You're viewing an older version of this GitHub Action. Do you want to see the latest version instead?
GitHub Action
publish node package action
v1.4.0
Publish a NodeJS package to NPM or GitHub Packages
PreRequirements
- Make sure you've stored a NPM Classic Token (an "Automation" token) as a secret in your repository. You can generate one at https://www.npmjs.com/settings/your-username/tokens.
- If you want to publish scope package, You need to apply to create an organization on npmjs.com,at https://www.npmjs.com/org/create.
jobs:
publish-npm:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- run: npm ci
- run: npm run build
- uses: cloudcome/publish-node-package-action@v1
with:
target: npm
token: ${{ secrets.NPM_TOKEN }}
PreRequirements
- Requires GitHub Packages write access
- No need to publish token
Notes
- GitHub Packages
name
may change after release, in two cases:- For example, the original name
my-pkg
will be changed to@owner/my-kg
, whereowner
is the name of the owner name of the current repository - For example, the original name
@my-scope/my-pkg
will be changed to@owner/my-scope__my-kg
, whereowner
is the owner name of the current repository
- For example, the original name
- The name attribute in package.json in the repository will not be modified
jobs:
publish-github:
runs-on: ubuntu-latest
permissions:
packages: write
steps:
- uses: actions/checkout@v3
- run: npm ci
- run: npm run build
- uses: cloudcome/publish-node-package-action@v1
with:
target: github
Name | Required | Default | Description |
---|---|---|---|
target |
true | None | Packages target, optionally npm /github |
token |
false | None | Target authorization token, GitHub Packages target does not need, internally has automatically obtained github.token |
tag |
false | latest |
The version label to release, the default is latest |
Nothing!