GitHub action to publish npm packages with semanantic versioning rules

Follow me, and consider starring the project to show your :heart: and support.

Table of Contents

• GitHub action to publish npm packages with semanantic versioning rules
  • Table of Contents
  • Semantic versioning over commit message
  • Action usage
    • Action Parameters
    • Complete action example
  • Action configuration Step-by-Step
    • Step1 - Secrets Configuration
    • Step 2
    • Step 3
    • Step 4
    • Step 5
  • Development
  • License
  • Buy me a Coffee

This action allow your project to create a new release, based on semantic versionig principles, and publish it to your npm registry.

Semantic versioning over commit message

To generate a new version (git tag and npm package publishing), you have just to add to the commit message one of the following key:

• [MAJOR] or [major]: new major release, e.g. v1.0.0 -> v2.0.0 will be executed
  • git commit -m "add best feature ever [major]"
• [PATCH] or [patch]: new patch release, e.g. v1.0.0 -> v1.0.1 will be executed
  • git commit -m "fix best feature ever [patch]"
• without any of the above keywords a new minor release will be executed, e.g. v1.0.0 -> v1.1.0
  • git commit -m "update best feature ever"

An new release is only exeuted on the defined target-branch (see Action Usage)

Action usage

Action Parameters

See action.yml

Name	Type	Default	Description
target-branch	string	master	Branch name new release should be executed
provenance	string	false	NPM package provenance

:heavy_exclamation_mark: When the Action Parameter provenance is set to true the id-token permission must be set to write:

1permissions:
2  id-token: write

Complete action example

1on:
2  push:
3    branches: master #the branch name must be the same of **target-branch**
4
5jobs:
6  publish:
7    runs-on: ubuntu-latest
8    permissions:
9      contents: write #allow to push on git repo
10      id-token: write #allow to publish npm package
11    steps:
12      - name: Checkout
13      id: checkout
14      uses: actions/checkout@v4 #checkout git repo
15      uses: actions/setup-node@v4 #setup node env
16      with:
17        node-version: 20.x
18        registry-url: 'https://registry.npmjs.org'
19    - name: Run my Action
20      id: run-action
21      uses: iuccio/npm-semver-publish-action@v1.0.0 #execute npm semver publish
22      with:
23        target-branch: master
24        provenance: true
25      env:
26        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} #npm token

Action configuration Step-by-Step

Step1 - Secrets Configuration

This action requires the NPM_TOKEN secret configuretion:

1. generate a new npm token able to publish Creating and viewing access tokens
2. add the above generated token in the secret NPM_TOKEN (see Using secrets in GitHub Actions)

Step 2

Add permissions to to push on git and publish on npm

1permissions:
2  contents: write
3  id-token: write

Step 3

Add to the checkout action:

1uses: actions/checkout@v4

Step 4

Add an actions/setup-node step to your workflow. If you have one already, ensure that the registry-url input is set (e.g. to https://registry.npmjs.org) so that this action can populate your .npmrc with authentication info:

1uses: actions/setup-node@v4
2with:
3  node-version: 20.x
4  registry-url: 'https://registry.npmjs.org'

Step 5

add actions/npm-semver-publish step:

1name: Run my Action
2id: run-action
3uses: iuccio/npm-semver-publish-action@v1.0.0
4with:
5  target-branch: 'master' #where a new release is applied
6  provenance: true #if you want to publish on npm registry the provenance
7env:
8  NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

That's it!

Development

See Development for more information.

License

CSVtoJSON is licensed under the GNU General Public License v3.0 License.

Buy me a Coffee

Just if you want to support this repository:

• BTC tip address: 37vdjQhbaR7k7XzhMKWzMcnqUxfw1njBNk