This is the documentation for the latest development version of Antrea. Both code and docs may be unstable, and these docs are not guaranteed to be up to date or correct. See the latest version.
This file documents the list of steps to perform to create a new Antrea
release. We use
<TAG> as a placeholder for the release tag (e.g.
Create a release branch for each new minor release (e.g
bug fixes, use the appropriate release branch.
Open a PR against the appropriate release branch with the following commits:
Make the release on Github with the release branch as the target: copy the
relevant section of the CHANGELOG for the release
description and check the
pre-release box if applicable. There is no need
to upload any assets as this will be done automatically by a Github workflow,
after you create the release.
After a while (time for the Github workflows to complete), check that:
antctlbinaries and yaml manifests). In particular, the following link should work:
Open a PR against the master branch with the following commits:
v0.1.0, the VERSION file should be updated to
v0.2.0-dev. If the release was for
v0.1.1, the VERSION file in the master branch is left untouched (should be