2.1 KiB
Steps to Release Minikube
Create a Release Notes PR
Assemble all the meaningful changes since the last release into the CHANGELOG.md file. See this PR for an example.
Build and Release a New ISO
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.
Bump the version in the Makefile
See this PR for an example.
Add the version to the releases.json file
Add an entry to the top of deploy/minikube/releases.json with the version, and 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.
Run integration tests
Run this command:
make integration
Investigate and fix any failures.
Tag the 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.
Build the Release
Run these commands:
GOOS=linux GOARCH=amd64 make out/minikube-linux-amd64
GOOS=darwin GOARCH=amd64 make out/minikube-darwin-amd64
Upload to GCS:
gsutil cp out/minikube-linux-amd64 gs://minikube/releases/$RELEASE/
gsutil cp out/minikube-darwin-amd64 gs://minikube/releases/$RELEASE/
Create a Release in Github
Create a new release based on your tag, like this one.
Upload the files, and calculate checksums.
Upload the releases.json file to GCS
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.json