Skip to content

Follow kernel.org point releases automatically; Linux 7.2.14 - #33

Merged
JBailes merged 1 commit into
mainfrom
feat/follow-stable
Oct 30, 2026
Merged

JBailes merged 1 commit into
mainfrom
feat/follow-stable

Conversation

@JBailes

@JBailes JBailes commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

SmoothKernel was four point releases behind (7.2.10; kernel.org published 7.2.14 today) because every point release needed a manual bump.

  • scripts/follow-stable.sh: finds the newest kernel.org stable/longterm release of the series in examples/smooth.env, waits until the tarball and its sha256sums entry are on the CDN, and updates KERNEL_VERSION in both env files. A newer series is reported as a notice; a series kernel.org no longer lists is a warning.
  • .github/workflows/follow-stable.yml: hourly (and on demand). Commits the bump to main and starts release.yml on main via workflow_dispatch (workflow-token pushes start no workflows). The release is built and attested exactly as any other commit to main.
  • Patch lanes and configs carry over within a series; docs/bumping-kernel.md now says point releases are automatic and keeps the manual steps for a new series.
  • This PR also moves to 7.2.14, so its own build checks that the lanes apply to the newest point release.

…x to 7.2.14

A Follow stable workflow checks kernel.org every hour. When a newer point
release of the series SmoothKernel builds is on the CDN, it commits the new
KERNEL_VERSION to main and starts the Release workflow, so urgent fixes reach
the Smooth* archive with no manual step. A new series is only reported.
@JBailes
JBailes merged commit 255b48f into main Oct 30, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant