Assemble all the meaningful changes since the last release into the CHANGELOG.md file. See this PR for an example.
This step isn't always required. Check if there were changes in the deploy directory. If you do this, bump the ISO URL to point to the new ISO, and send a PR.
See this PR for an example.
Run this command:
make integrationInvestigate and fix any failures.
Run this command:
make cross checksumAdd an entry to the top of deploy/minikube/releases.json with the version and checksums. Send a PR. This file controls the auto update notifications in minikube. Only add entries to this file that should be released to all users (no pre-release, alpha or beta releases). The file must be uploaded to GCS before notifications will go out. That step comes at the end.
The schema for this file can be found in deploy/minikube/schema.json.
An automated test to verify the schema runs in Travis before each submit.
gsutil cp out/minikube-linux-amd64 gs://minikube/releases/$RELEASE/
gsutil cp out/minikube-linux-amd64.sha256 gs://minikube/releases/$RELEASE/
gsutil cp out/minikube-darwin-amd64 gs://minikube/releases/$RELEASE/
gsutil cp out/minikube-darwin-amd64.sha256 gs://minikube/releases/$RELEASE/
gsutil cp out/minikube-windows-amd64.exe gs://minikube/releases/$RELEASE/
gsutil cp out/minikube-windows-amd64.exe.sha256 gs://minikube/releases/$RELEASE/Run a command like this to tag it locally: git tag -a v0.2.0 -m "0.2.0 Release".
And run a command like this to push the tag: git push upstream v0.2.0.
Create a new release based on your tag, like this one.
Upload the files, and calculated checksums.
This step makes the new release trigger update notifications in old versions of Minikube. Use this command from a clean git repo:
gsutil cp deploy/minikube/releases.json gs://minikube/releases.jsongsutil cp -r gs://minikube/releases/$RELEASE gs://minikube/releases/latest