We use yarn workspaces, please use
Make sure that associated services are available on the localhost - e.g.
[skip ci] to commit message to skip running CI.
We use semver standard.
Every commit to master triggers CI via GH Actions, which builds new docker images, assign tags and pusher the new images to DockerHub.
After pushing a new tagged please go ahead and create a new Github release with a summary and attributions.
Pushing to master automatically created new docker images with
yarn release to create a new release.
Push to master. Push to master, together with tags
git push origin master --tags. Pushing to master will trigger CI that will actually update dockerhub.
Pushing a properly formatted (semver) git tag starts release of dockerhub images tagged accordingly. E.g.
v0.5.2 will release dockerhub tags
v0, v0.5, v0.5.2.
The script does the following behind the scenes:
package.json files (we release all together and do not increase / release individual packages version)
Commit with message, e.g.
Add git tag, e.g.
git tag v0.5.2