This process will create a new tagged release of flux, push dockerfiles and upload the fluxctl binary to GitHub releases.
- Circle CI must have a secret environmental variable called
GITHUB_TOKENwhich is a personal access token.
- Alter and commit the /CHANGELOG.md file to signify what has changed in this version.
- Ensure example deployment is up-to-date. (Check image tags) 3 Push that to a PR and have it reviewed. 3.1 Merge!
- Create a new release: https://github.com/weaveworks/flux/releases/new
- Fill in the version number for the name and tag. The version number should conform to semver; i.e., look like
1.2.3(NB: no leading 'v'); optionally with a pre-release suffix, e.g.,1.0.0-beta - Fill in the Description field (possibly a copy paste from the CHANGELOG.md)
- Click "Publish release"
- Add a new release to https://checkpoint-api.weave.works/admin
Circle will then run the build and upload the built binaries to the "Downloads" section of the release.
The most recent binaries are always available at: https://github.com/weaveworks/flux/releases/latest