This whole document is ordered as per occurence of events by time.
1. Context
- Commit/Merge on
main branch
- Run
npm version patch or npm version minor command locally (this updates package.json, and creates another commit)
- Push the changes to
main branch from local machine
- Open GitHub and create a Release and a new tag (eg. v0.3.0 or v0.2.1), and publish it
2. Automation (problematic)
- Make sure on GitHub you have a variable
NODE_AUTH_TOKEN
- on L17 of
release.yml file it should automatically create a .npmrc file
- Publishing the release will trigger the
release.yml github action workflow which will automatically publish to npm registry
3. Output (remote)
This is the output of the publish action triggered on release
4. Manual publish (running fine)
- Make sure that locally you have
~/.npmrc file
//registry.npmjs.org/:_authToken=<auth-token>
- Replace with the auth token of the npm package owner
- Run
npm publish command locally to publish the pacakge to npm registry manually
5. Output (local)
This is the output of running npm publish command locally

This whole document is ordered as per occurence of events by time.
1. Context
mainbranchnpm version patchornpm version minorcommand locally (this updates package.json, and creates another commit)mainbranch from local machine2. Automation (problematic)
NODE_AUTH_TOKENrelease.ymlfile it should automatically create a.npmrcfilerelease.ymlgithub action workflow which will automatically publish to npm registry3. Output (remote)
This is the output of the
publishaction triggered onrelease4. Manual publish (running fine)
~/.npmrcfilenpm publishcommand locally to publish the pacakge to npm registry manually5. Output (local)
This is the output of running
npm publishcommand locally