Unomi tracker: Versioning and release


Current repository is using Trunk based development.

  • main: Used for latest currently develop version
  • 1_x: Used for maintenance branches of previous versions
  • UNOMI-XXX: feature or bug fix branches used to create pull request targeting the main branch

Release example for 1.1.0

Checks before starting the release process:

Start the release process:

  • Check version and create Git tag:
    • Check package.json is using correct version: 1.1.0
    • Create Git tag: git tag -s v1.1.0 -m 'create v1.1.0 tag' (-s is used for signing using your local git GPG config)
    • Push the tag: git push origin v1.1.0
  • Sign the package and upload the package to Apache SVN.
    • Download the .tar.gz source package from Git previously created tag.
    • Sign the package: gpg -ab unomi-tracker-1.1.0.tar.gz.
    • Verify the signature: gpg --verify unomi-tracker-1.1.0.tar.gz.asc unomi-tracker-1.1.0.tar.gz (Check that the signature is correctly using your Apache signature)
    • SHA the package: shasum -a 512 unomi-tracker-1.1.0.tar.gz > unomi-tracker-1.1.0.tar.gz.sha512
    • Upload the 3 files (.tar.gz, .tar.gz.asc, .tar.gz.sha512) to Apache SVN: (Create the folder if it doesn't exist)
  • Start voting process, follow Unomi documentation it's the same:
  • Wait for the vote to finnish then finalize the release on Apache side:
    • move to
    • in JIRA mark the version unomi-tracker-1.1.0 as released and add a release date
  • Publish the release package to NPM:
    • Download the Apache released package:
    • Untar the package and publish the package by running: npm publish
  • You can set the next version into package.json like 1.2.0 for example.