ci(bpfcompat): test the v0.4.0 release candidate - #3076
Open
ErenAri wants to merge 1 commit into
Open
Conversation
Signed-off-by: ErenAri <erenari27@gmail.com>
Contributor
|
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ErenAri The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Contributor
Author
|
Fork dress rehearsal passed at the exact PR head 3c8ecc3: https://github.com/ErenAri/libs/actions/runs/31120313517
This manual run proves the pin fix. The first successful upstream schedule run after merge will remain the graduation evidence. |
35 tasks
Perf diff from master - unit testsHeap diff from master - unit testsHeap diff from master - scap fileBenchmarks diff from master |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3076 +/- ##
=======================================
Coverage 76.56% 76.56%
=======================================
Files 301 301
Lines 33693 33693
Branches 5038 5038
=======================================
Hits 25797 25797
Misses 7896 7896
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Advance the non-blocking bpfcompat compatibility lane from the v0.3.6 release commit to the exact v0.4.0-rc.3 release-candidate commit.
The first scheduled run after #3061 failed in the Action setup step before any VM target ran:
https://github.com/falcosecurity/libs/actions/runs/30792162435
The v0.3.6 Action downloads the amd64 CLI, amd64 validator, and the release SHA256SUMS, then asks sha256sum to validate every entry. Because that checksum file also lists the arm64 CLI, the amd64 job fails with:
v0.4.0-rc.3 fixes the consumer path by validating only the selected assets and verifying GitHub attestations. Its manual, T+24h, and T+72h canaries all passed against the immutable release commit and image digest.
This one-line exact-SHA update lets the lane reach the real scap-open loader and expanded kernel matrix again. It does not make the scheduled lane blocking.
Which issue(s) this PR fixes:
Follow-up to #3023, #3024, and #3061.
Special notes for your reviewer:
The next scheduled run is Monday, August 10 at 06:00 UTC. A successful schedule after this merges will provide the external ecosystem evidence for bpfcompat v0.4.0 graduation.
Does this PR introduce a user-facing change?:
release-note: NONE