-
Notifications
You must be signed in to change notification settings - Fork 60
Closed
Description
- Release preparations
- Run release GH action
- Use the given release branch and set the Draft release checkbox so it's possible to edit the draft release before publishing.
- https://github.com/istio-ecosystem/sail-operator/actions/runs/22388265793
- Verify the operator was published to the operator hub
- Test fresh installation and upgrade from the previous version from the operator hub.
- Edit the GH release notes draft in tag section
- If the release notes are huge and were created incorrectly, use compare to see differences between versions (e.g. 1.28.3->1.29.0 1.28.3...release-1.29 ) and rewrite release notes ( you can help with AI tool ). Remove non-important changes as tests, documentations and automation commits
- https://github.com/istio-ecosystem/sail-operator/releases/tag/1.29.0
- Publish the tag
- Trigger Publish Helm artifact GH workflow and review the created PR. Note that the release notes must be published already.
- Test the installation using the helm chart by following the documentation. You will need a fresh cluster, as there are some conflicts if the Sail Operator was installed earlier. Or you can try to remove the sail CRDs and cluster roles.
- Announce in #sail-operator channel in Istio Slack
Reactions are currently unavailable