From 7262240468cc3a538a97ea8809765aba69b2b067 Mon Sep 17 00:00:00 2001 From: ErenAri Date: Sat, 27 Jun 2026 22:23:40 +0300 Subject: [PATCH] docs: bump stale GitHub Action refs to @v0.2.0 (version consistency) Integrity sweep after the v0.2.0 release: several "how to use the action" examples still pinned @v0.1.6 / @v0.1.3. Bumped all forward-looking `uses: Kernel-Guard/bpfcompat@...` refs to @v0.2.0 across README, quickstart, the Falco case study, the suite doc, and the external-CI proof. No historical run records changed. Co-Authored-By: Claude Opus 4.8 --- README.md | 4 ++-- docs/case-study-falco-modern-bpf.md | 2 +- docs/external-ci-proof.md | 2 +- docs/project-compatibility-suite.md | 2 +- docs/quickstart.md | 4 ++-- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 8b8dc9a..0b1a6a4 100644 --- a/README.md +++ b/README.md @@ -511,7 +511,7 @@ or the Firecracker lane. See Suite mode (recommended — gates the whole collection): ```yaml -- uses: Kernel-Guard/bpfcompat@v0.1.6 +- uses: Kernel-Guard/bpfcompat@v0.2.0 with: suite: suites/project.yaml suite-out: reports/suite.json @@ -525,7 +525,7 @@ are alive and adds the result to the suite-level collection matrix. Single artifact: ```yaml -- uses: Kernel-Guard/bpfcompat@v0.1.6 +- uses: Kernel-Guard/bpfcompat@v0.2.0 with: artifact: path/to/program.bpf.o manifest: path/to/manifest.yaml diff --git a/docs/case-study-falco-modern-bpf.md b/docs/case-study-falco-modern-bpf.md index a0c9139..7c27bd6 100644 --- a/docs/case-study-falco-modern-bpf.md +++ b/docs/case-study-falco-modern-bpf.md @@ -49,7 +49,7 @@ That is the difference between "❌ it broke" and "❌ ring buffer isn't availab ```bash # In CI (GitHub Action), against your kernel matrix: -- uses: Kernel-Guard/bpfcompat@v0.1.6 +- uses: Kernel-Guard/bpfcompat@v0.2.0 with: artifact: build/bpf_probe.o matrix: matrices/mvp.yaml diff --git a/docs/external-ci-proof.md b/docs/external-ci-proof.md index 75d937a..a0cb506 100644 --- a/docs/external-ci-proof.md +++ b/docs/external-ci-proof.md @@ -17,7 +17,7 @@ that compatibility failures block CI with `rc=2`. - - -Public repositories can reference `Kernel-Guard/bpfcompat@v0.1.3` directly. +Public repositories can reference `Kernel-Guard/bpfcompat@v0.2.0` directly. ## Source Refs Validated diff --git a/docs/project-compatibility-suite.md b/docs/project-compatibility-suite.md index ffe4098..7735830 100644 --- a/docs/project-compatibility-suite.md +++ b/docs/project-compatibility-suite.md @@ -114,7 +114,7 @@ Single-artifact mode remains supported. Suite mode is enabled by setting `suite`: ```yaml -- uses: Kernel-Guard/bpfcompat@v0.1.3 +- uses: Kernel-Guard/bpfcompat@v0.2.0 with: suite: suites/dev-functional.yaml suite-out: reports/bpfcompat-suite.json diff --git a/docs/quickstart.md b/docs/quickstart.md index 27d5a72..2595b60 100644 --- a/docs/quickstart.md +++ b/docs/quickstart.md @@ -35,7 +35,7 @@ jobs: runs-on: ubuntu-latest # exposes /dev/kvm for KVM acceleration steps: - uses: actions/checkout@v4 - - uses: Kernel-Guard/bpfcompat@v0.1.6 + - uses: Kernel-Guard/bpfcompat@v0.2.0 with: artifact: build/program.bpf.o # your compiled object matrix: matrices/mvp.yaml # the kernels you support @@ -57,7 +57,7 @@ What you get: Shipping a whole product? Use **suite mode** to gate a collection in one run: ```yaml - - uses: Kernel-Guard/bpfcompat@v0.1.6 + - uses: Kernel-Guard/bpfcompat@v0.2.0 with: suite: suites/project.yaml suite-out: reports/suite.json