Skip to content

Latest commit

 

History

History
27 lines (18 loc) · 1.22 KB

release.md

File metadata and controls

27 lines (18 loc) · 1.22 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

This project adheres to Semantic Versioning.

Also, note that the plugin-sdk-go version is NOT paired with the Falco version nor with the Plugin API version. However, any backward-incompatible changes introduced by Plugin API represent a breaking change for the plugin-sdk-go too. In such a case, the major version (or the minor version when major version is zero) MUST be incremented.