[Tracking] Falco 0.36.0 RC1

[leogr]

Why?

Per the Falco Roadmap Management Proposal introduced by these release cycles, a Falco pre-release (or a viable development build) is expected during the last week of each iteration to ensure adequate testing and QA.

This issue is to track the release of Falco 0.36.0 RC1 for the above-stated purpose.

ETA: ASAP early Sept.

Note: We planned to complete the "Stabilization" iteration in August, which should have resulted in a Falco pre-release. However, due to many maintainers and contributors being on vacation in the recent weeks, and as this is our first time implementing this new approach, we're running a bit behind schedule. This delay is still acceptable. Our realistic goal is to finalize Falco 0.36.0 RC1 around the 1st or the 2nd week of September.

Status

Blockers

Preview Give feedback

1. update: split falco_rules.yaml according to the rules maturity rules#149
   approved dco-signoff: yes kind/cleanup kind/feature lgtm size/XXL +6
   
2. rules 2.0.0 pre-release (including changes due to the newly introduced Rules Maturity Framework)
3. libs 0.13 release
4. update(cmake/modules): bump rules to falco-rules-2.0.0-rc1 #2775
   approved dco-signoff: yes kind/feature lgtm release-note-none size/S +6
   

   

Nice-To-Have

Preview Give feedback

1. Plugins (pre-)releases
2. falcoctl v0.6.0 release
3. [TRACKING] Phase 4 - Tag Falco rules according to rules maturity framework and compliance use case if applicable rules#126
   kind/feature +1
4. new(falco): update the Falco base image to debian 12 #2718
   approved area/build area/ci dco-signoff: yes kind/feature lgtm release-note size/XL +8
   

   

[FedeDP]

PR to bump drivers to 6.0.0+driver and libs to 0.13.0-rc1: #2783

[FedeDP]

https://github.com/falcosecurity/falco/releases/tag/0.36.0-rc1 was released!
It uses libs 0.13.0-rc1 and driver 6.0.0+driver.

[FedeDP]

Note: we can manage multiple RCs; we might want a new RC with bumped plugins and 0.13.0 libs.