Release Process

Releases must follow a specific order of operations. The library and website may be released separately.

The package

• Bump version

  • Update the version number following semver standards in package.json
  • Update readme.md in the root directory with the same version number as in package.json
  • Update ./docs/_config.yml library_version to same version as in package.json

• Build icons

  • Run gulp icons to generate the icon font and SCSS files.

• Build package

  • Run gulp build:dist --production to compile the full library and standalone component CSS files, expanded and minified.

• Tag release

• Publish package

  • Run npm publish to push the package to npm registry

• Deploy to CDN

  • Current temp solution is to update the directory to match the version number.
  • Bamboo Plan link - https://bamboo.hybris.com/build/admin/edit/editBuildTasks.action?buildKey=PTW-USPRODTECHNE2-DJ
  • Update task "copy techne 2.0 to techne page"

The docs

• Create a new release branch
  • Make sure all pull requests are reviewed, tested and merged prior to creating a release branch
• Create a new release tag in github
  • Select the newly created release branch
  • The release tag name should match the release branch number
• Draft a new release with releas notes
• Publish Release on github