The Spinnaker team is committed to providing a regular release cadence in order to help users understand when new features will be available, as well as help non-core developers plan to get their features released in the next stable version of Spinnaker.
Cutting the Release Branches
Every eight weeks, we cut release branches for the upcoming release. If the
version we intend to release is
M.N, a branch with the name
cut in each component repository. For example, see the state of the
repository leading up
to the 1.6 release:
We call this snapshot of all the Spinnaker repositories the “Release Candidate”.
Running the Release Candidate
Once these release branches are cut, anyone can run the release candidate using
# this would be version 'release-1.6.x-latest-unvalidated' for 1.6 hal config version edit --version release-M.N.x-latest-unvalidated hal deploy apply
Patching the Release Candidate
Warning“Do not merge feature code into a release branch, only fixes are accepted.
Unless a severe error (e.g. security vulnerability, large-scale breakage) has a pending patch, patch releases are published at a weekly cadence on a best-effort basis.
Marking the Release Candidate Stable
Once the community has deemed that the Candidate is “stable” (meaning all
passing, and no known issues or regressions remain), we will release Spinnaker
M.N.0. Further patches can be merged into the release branch for
future patch releases (e.g.
There’s a public calendar you can subscribe to which includes important release dates.
- If you use Google Calendar, subscribe .
- If you don’t use Google Calendar or have trouble with the first link, you can copy this iCal URL to subscribe using your calendar app of choice (instructions for
- If you don’t want to subscribe directly, you can check the calendar below: