Releasing¶
-
Ensure that the
release branch
already exist. -
Checkout the release branch. Example:
git fetch upstream && git checkout release-1.5
-
Run the script found at
hack/trigger-release.sh
as follows:
./hack/trigger-release.sh <version> <remote name>
Example:
./hack/trigger-release.sh v1.6.0-rc1 upstream
Tip
The tag must be in one of the following formats to trigger the GH workflow:
* GA: v<MAJOR>.<MINOR>.<PATCH>
* Pre-release: v<MAJOR>.<MINOR>.<PATCH>-rc<RC#>
Once the script is executed successfully, a GitHub workflow will start
execution. You can follow its progress under the Actions tab, the name of the action is Release
.
- When the action completes, visit the generated draft Github releases and enter the details about the release:
- Getting started (copy from previous release and new version)
- Changelog
Update Brew formula¶
-
Update Brew formula:
-
Fork the repo https://github.com/argoproj/homebrew-tap
- Run the following commands to update the brew formula:
cd homebrew-tap ./update.sh kubectl-argo-rollouts $VERSION
- If there is a new minor version we want to update the versioned formula as well:
- Run the following commands to update the versioned brew formula:
./update.sh kubectl-argo-rollouts $VERSION @<version_without_patch_and_v>
- Example: If the new version is
v1.3.2
, we want to update the formula forv1.3
as well../update.sh kubectl-argo-rollouts v1.3.2 @1.3
- Run the following commands to update the versioned brew formula:
- Commit and push the changes to your fork
git commit -am "Update kubectl-argo-rollouts to $VERSION"
- Create a PR with the modified files pointing to upstream/master
- Once the PR is approved by a maintainer, it can be merged.
Verify¶
-
Install locally using the command below and follow the Getting Started Guide:
kubectl apply -n argo-rollouts -f https://github.com/argoproj/argo-rollouts/releases/download/${VERSION}/install.yaml
-
Check the Kubectl Argo Rollout plugin:
brew upgrade kubectl-argo-rollouts kubectl argo rollouts version