Release and its automated processes

This page contains relevant information about automated processes / utilities that can be used in a release cycle.

Publishing an updated package

We have a CircleCI workflow, which runs only on main or stable-* branches. The essence of the workflow is the following:

for each package:
    if last commit contains version change:
        publish package to npm

If you want to bump package version and publish it to npm registry, your version change should be exactly in the last commit. This is because of two things:

1. If multiple commits are merged to main branch at the same time, CircleCI will execute workflows only once on top of the latest commit.
2. To determine that version was changed we evaluate the difference between HEAD and HEAD~1.

Example script output, where no package versions were changed: