RELEASING.md

Releasing

1. Checkout a clean Tracker branch from upstream (instead of using your own). This will help with wrong tags you might have locally (by not uploading them by accident).

   gh clone khulnasoft/tracker

2. Prepare release by creating the PR with the following changes

   1. Check if a libbpfgo update is needed (needs to be released first).
   2. Check if libbpf version is the same as libbpfgo's libbpf version.
   3. Update types module to latest.
   4. Update the container image tag, with the one to be released, at: deploy/kubernetes/tracker/tracker.yaml
   5. Update home, version and appVersion properties in deploy/helm/tracker/Chart.yaml - example
   6. Create a PR with the tags bump

3. Run tests and checks

   1. Manually run a snapshot release from its workflow.
   2. Sanity checks features that might not have specific tests:
      1. multiple policy files simultaneously (check event results)
      2. network capture (pcap files)
      3. other capture (files, memory, etc...)
      4. other ...

4. Create a git tag and push it to the upstream. This will trigger the .github/workflows/release.yaml workflow.

   git tag -v0.99.0
   git push upstream v0.99.0

5. Verify that the release workflow has built and published the artifacts.

   1. Tracker binaries (tracker, tracker-ebpf, tracker-static, tracker-ebpf-static, tracker-rules, signatures) in the form of a tar archive tracker.<VERSION>.tar.gz
   2. Source code zip and tar files
   3. Docker images pushed to the khulnasoft/tracker repository.

6. Publish the Helm chart by triggering workflow .github/workflows/publish-helm.yaml.