Create the collector image release branch
- Navigate to the local stackrox/collector git repository directory on the master branch and ensure the local checked out version is up to date.
git checkout master
git pull
- Set the release environment variable, which should be incremented from the previous released version.
export COLLECTOR_RELEASE=3.8
- Create an internal release tag to mark on the master branch where we forked for the release.
git tag "${COLLECTOR_RELEASE}.x"
git push origin "${COLLECTOR_RELEASE}.x"
- Create the release branch with an empty commit and push.
git checkout -b "release-${COLLECTOR_RELEASE}"
git commit --allow-empty -m "Empty commit to diverge ${COLLECTOR_RELEASE} from master"
git push --set-upstream origin "release-${COLLECTOR_RELEASE}"
- Set the patch number and release environment variables (if not set). See the section "Patch releases" for patch releases
export COLLECTOR_PATCH_NUMBER=0
export COLLECTOR_RELEASE=3.8
- Tag and push the release.
git tag -a "${COLLECTOR_RELEASE}.${COLLECTOR_PATCH_NUMBER}"
git push origin "${COLLECTOR_RELEASE}.${COLLECTOR_PATCH_NUMBER}"
- Create and push a tag to the falcosecurity-libs repository
git submodule update --init falcosecurity-libs
cd falcosecurity-libs
git tag -a "${COLLECTOR_RELEASE}.${COLLECTOR_PATCH_NUMBER}"
git push origin "${COLLECTOR_RELEASE}.${COLLECTOR_PATCH_NUMBER}"
Patch releases
There is a script at utilities/tag-bumper.py for creating new tags for patch releases. That script is out of date and will be updated.
- Navigate to your local stackrox/collector repo and run:
git checkout release-"${COLLECTOR_RELEASE}"
- Make changes by cherry-picking or otherwise and commit changes.
- Increment COLLECTOR_PATCH_NUMBER
- Tag and push the patch
git tag -a "${COLLECTOR_RELEASE}.${COLLECTOR_PATCH_NUMBER}"
git push --follow-tags
- Create a pull request to update the
COLLECTOR_VERSION
file in the stackrox/stackrox repo with the newly create release after CI images have been built.