Skip to content

Latest commit

 

History

History
29 lines (23 loc) · 966 Bytes

RELEASING.md

File metadata and controls

29 lines (23 loc) · 966 Bytes

RELEASING

Automated releases to NPM are not supported at this time to prevent exposing valid NPM token paths to the public.

Steps

We recommend the following steps to manually release a version:

  • Create a PR with your changes including a version bump in package.json following the conventional commits specification.

  • Merge the PR after reviews and approvals from the team.

  • Log in to the Contentsquare NPM (request write access in the team) and publish using the commands below

    npm login
    npm publish --access public
  • You can publish a beta version to test your PR before merging using the commands:

    npm login
    npm publish --tag beta
  • Check the NPM registry to verify that your release was published

    # fetch the latest version
    npm show @contentsquare/tag-sdk version
    
    # fetch all versions
    npm show @contentsquare/tag-sdk versions --json