-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.16.1 release #1581
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Install
gh
and authenticate with GitHub by runninggh auth login
.Install the latest Cilium release tool:
Define
NEW_RELEASE
andPREVIOUS_RELEASE
environment variables. Forexample, if you are releasing a new Hubble CLI version based on
Cilium 1.16.1
with the previous release beingCilium 1.16.0
:Create a release prep branch:
Check if
replace
directive ingo.mod
is in sync withcilium/cilium
. Run:and copy the
replace
directive togo.mod
if it's out of sync.Update Cilium dependency:
Prepare release notes:
Modify
CHANGELOG.md
with the generated release notes:Push the prep branch and open a Pull Request against main branch.
Get the pull request reviewed and merged.
Update your local checkout:
Set the commit you want to tag:
Usually this is the most recent commit on
main
, i.e.Create a tag:
Admire the tag you just created for 1 minute:
Then push the tag:
Ping
hubble-maintainers
team on Slack to get an approval to runImage Release Build workflow.
Wait for the
Create a release
workflow to finish.Find the release draft in the Releases page. Copy and paste release notes from
CHANGELOG.md, and click on
Publish release
button.Post a release announcement message in the Cilium Slack #general channel. Example:
Update the Releases section of the
README.md
to point to the latestrelease.
Update
stable.txt
in the main branch:and then open a pull request against the
main
branch, get it reviewed and merged.The text was updated successfully, but these errors were encountered: