Skip to content

Latest commit

 

History

History
25 lines (16 loc) · 1.21 KB

release.md

File metadata and controls

25 lines (16 loc) · 1.21 KB
Raw

Release Process

When we release we do the following process:

  1. We decide together (usually in the #falco channel in slack) what's the next version to tag
  2. A person with repository rights does the tag
  3. The same person runs commands in their machine following the "Release commands" section below
  4. The tag is live on Github with the changelog attached

Release commands

Just tag the version. For example:

git tag -a v0.1.0-rc.0 -m "v0.1.0-rc.0"
git push origin v0.1.0-rc.0

The goreleaser will run on CircleCI and do the magic :)

About versioning

Basically, this project adheres to Semantic Versioning.

Furthermore, although the go-client version is NOT paired with the Falco version directly, the major version MUST be incremented when any backwards incompatible changes are introduced to the proto definitions. The only notable exception is major version zero, indeed, for initial development just the minor version MUST be incremented.