Skip to content

Latest commit

 

History

History
49 lines (42 loc) · 1.38 KB

File metadata and controls

49 lines (42 loc) · 1.38 KB

How to Publish

Only appointed team members may publish releases.

Automated Release (Bash Scripts)

  1. (one time) Login to npm via:
    npm login
  2. Run the release preparation script:
    ./bin/release-prepare.sh
  3. Create and merge the PR.
  4. Run the release publish script:
    ./bin/release-publish.sh vN.N.N
    (where N.N.N is the version tag)

Manual Release Steps

Instructions
  1. (one time) Login to npm via:
    npm login
  2. Create new branch for version bump.
  3. Verify build is up-to-date:
    npm run build:css
    Commit substantial unexpected changes via independent PR.
  4. Update version via:
    npm version vN.N.N
    (where N.N.N is the version tag)
  5. Build with new version:
    npm run build:css
  6. Commit, push, PR, review, merge.
  7. Publish to NPM via:
    npm publish --access public
    Project build will automatically occur before publish.
  8. Create release and tag on GitHub.
  9. Fetch the latest tags.
    git fetch --tags
  10. Check whether tag is annotated.
    git describe --always
    (expect vN.N.N i.e. the version tag)
  11. If tag is not annotated, then:
    1. Annotate Github's tag:
      bin/annotate-tag.sh vN.N.N
      (where N.N.N is the version tag)
    2. Overwrite remote tag with annotated one:
      git push --tags --force