Skip to content

Latest commit

 

History

History
51 lines (32 loc) · 1.48 KB

release.md

File metadata and controls

51 lines (32 loc) · 1.48 KB
Raw

Releasing Fleet

  1. Update the CHANGELOG with the changes that have been made since the last Fleet release.

  2. Tag and push the new release in Git:

git tag <VERSION>
git push origin <VERSION>
  1. Build the new binary bundle (ensure working tree is clean because this will effect the version string built into the binary):
make binary-bundle
  1. Create a new release on the GitHub releases page. Select the newly pushed tag (GitHub should say "Existing tag"). Use the version number as the release title. Use the below template for the release description (replace items in <> with the appropriate values):
### Changes

<COPY FROM CHANGELOG>

### Upgrading

Please visit our [update guide](https://github.com/kolide/fleet/blob/master/docs/infrastructure/updating-fleet.md) for upgrade instructions.

### Documentation

Documentation for this release can be found at https://github.com/kolide/fleet/blob/<VERSION>/docs/README.md

### Binary Checksum

```
sha256sum fleet.zip
<HASH VALUE>  fleet.zip
```

Upload the fleet.zip binary bundle and click "Publish Release".

  1. Push the new version to Docker Hub (ensure working tree is clean because this will effect the version string built into the binary):
make docker-push-release
  1. Announce the release in the #kolide channel of osquery Slack.