Note
The steps outlined in this document can only be performed by maintainers or administrators of this project.
The release automation is based on Github
Actions and has been improved over time
to simplify the experience for creating govmomi
releases.
The Github Actions release workflow
uses goreleaser
and automatically creates/pushes:
- Release artifacts for
govc
andvcsim
to the release page, includingLICENSE.txt
,README
andCHANGELOG
- Docker images for
vmware/govc
andvmware/vcsim
to Docker Hub - Source code
Releases are not tagged on the main
branch, but a dedicated release branch, for example release-0.35
.
git checkout main
git fetch -avp
git diff main origin/main
# if your local and remote branches diverge run
git pull origin/main
Warning
These steps assume
origin
to point to the remotehttps://github.com/vmware/govmomi
, respectivelygit@github.com:vmware/govmomi
.
For new releases, create a release branch from the most recent commit in
main
, e.g. release-0.35
.
export RELEASE_BRANCH=release-0.35
git checkout -b ${RELEASE_BRANCH}
For maintenance/patch releases on existing release branches, simply checkout the existing release branch and add commits to the existing release branch.
Warning
Run the following commands and commit any changes to the release branch before proceeding with the release.
make doc
./scripts/contributors.sh
if [ -z "$(git status --porcelain)" ]; then
echo "working directory clean: proceed with release"
else
echo "working directory dirty: please commit changes"
fi
# perform git add && git commit ... in case there were changes
Warning
Do not create a tag as this will be done by the release automation.
The final step is pushing the new/updated release branch.
git push origin ${RELEASE_BRANCH}
Open the govmomi
Github repository and
navigate to Actions -> Workflows -> Release
.
Click Run Workflow
which opens a dropdown list.
Select the new/updated branch, e.g. release-0.35
, i.e. not the main
branch.
Specify a semantic tag
to associate with the release, e.g. v0.35.0
.
Warning
This tag must not exist or the release will fail during the validation phase.
By default, a dry-run is performed to rule out most (but not all) errors during
a release. If you do not want to perform a dry-run, e.g. to finally create a
release, deselect the Verify release workflow ...
checkbox.
Click Run Workflow
to kick off the workflow.
After successful completion and if the newly created tag
is the latest
(semantic version sorted) tag in the repository, a PR is automatically opened
against the main
branch to update the CHANGELOG
.