Experimental extraction/refactoring of the Operator SDK's ansible operator plugin
upstream
that points to this repositorySince this project is currently consumed as a library there are some manual steps that need to take place prior to creating a release. They are as follows:
main
branch:
git checkout main
main
branch is up to date:
git fetch upstream && git pull upstream main
git checkout -b release/prep-vX.Y.Z
ImageVersion
variable in internal/version/version.go
to be the version you are prepping for releaseexport IMAGE_VERSION
in Makefile
to be the version you are prepping for releasemake generate
main
branchmain
branch:
git checkout main
git fetch upstream && git pull upstream main
release-vX.Y
. In this example we will create a branch for a v0.2.0
release:
git checkout -b release-v0.2
git push -u upstream release-v0.2
git tag -a -s -m "ansible-operator-plugins release v0.2.0" v0.2.0
git push upstream v0.2.0
/cherry-pick release-vX.Y
where X is the major version and Y is the minor version. An example of cherry picking for a v0.2.1
release would be:
/cherry-pick release-v0.2
v0.2.1
release:
git checkout release-v0.2
git fetch upstream && git pull upstream release-v0.2
git tag -a -s -m "ansible-operator-plugins release v0.2.1" v0.2.1
git push upstream v0.2.1
[!NOTE] While the release process is automated once the tag is pushed it can occasionally timeout. If this happens, re-running the action will re-run the release process and typically succeed.