Examples:

• Right: ^1.0.17-staging.5
• Wrong: ^1.0.17-staging-5. Notice that the last dash is now the one preceding the number 5. This will break usage of the caret when npm tries to fetch this

To make sure you don't end up violating this convention, see the following guide.

1. Bump the version field in package.json:

   • Staging:
     1. Switch to the staging branch.
     2. make release-staging
   • Production:
     1. Switch to the main branch.
     2. make release

2. Push your changes including any git tags created:

   git push
   git push --tags

3. Trigger the GitHub Action in charge of publishing the new NPM package if needed.

• Staging packages are built and published automatically when tags include the word staging.
• On production you instead have to explicitly create a release.