Repository navigation
Add weekly workflow to notify on libbpf updates - #62
Open
gregclermont wants to merge 1 commit into
Open
gregclermont wants to merge 1 commit into
gregclermont wants to merge 1 commit into
Conversation
Unlike vmlinux.h, upstream libbpf release tags are permanent (no silent-rotation hazard) and bumping the bundled .so is an ABI-sensitive, multi-step change (build+publish the libbpf-v<ver> release assets, then bump .libbpf-version, rebuild the compile image, rebuild the wheel). So rather than auto-opening a bump PR, this scheduled job only notifies: when a newer same-major libbpf release exists upstream it opens (once, deduped) a tracking issue with the bump runbook. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This branch has not been deployed
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.
Adds
.github/workflows/check-libbpf.yml— a scheduled (weekly, Tuesdays 06:00 UTC) + manually-dispatchable job that notifies when a newer libbpf is available, rather than auto-bumping.Why notify instead of auto-PR (unlike the vmlinux.h job)
vmlinux.h'smainbranch does. This is a stay-current update, low urgency..soloaded via ctypes (bindings.pydeclares argtypes/restypes), so a bump deserves human ABI review, not auto-merge.libbpf-v<ver>release assets first (viabuild-libbpf.yml); otherwisemake setup-linuxand the wheel build 404. A self-validating one-file bump PR isn't possible.What it does
src/tinybpf/.libbpf-versionand finds the highest upstream tag in the same major series (so a future2.0never auto-notifies a major jump).libbpf-updatelabel exists and opens a tracking issue with the bump runbook — deduped: skips if an open issue already mentions that version.At the current pin (
1.4.0) the latest1.xis1.7.0, so the first run will open a tracking issue.Notes
issues: write+contents: read.🤖 Generated with Claude Code