Skip to content

ci: track latest stable LLVM major via Renovate - #81

Merged
zeriyoshi merged 1 commit into
mainfrom
ci/renovate-llvm-version
Jul 27, 2026
Merged

ci: track latest stable LLVM major via Renovate#81
zeriyoshi merged 1 commit into
mainfrom
ci/renovate-llvm-version

Conversation

@zeriyoshi

Copy link
Copy Markdown
Contributor

Summary

The Dockerfile pinned clang/LLVM to a hardcoded 22 with no mechanism to learn about newer stable releases. This makes the version Renovate-managed:

  • Dockerfile: new LLVM_VERSION build argument (global + per-stage), replacing all hardcoded occurrences — the apt.llvm.org repository line, 12 package names, and 8 update-alternatives registrations across the base and devcontainer stages
  • renovate.json: a regex custom manager (same pattern as the Valgrind one) tracking llvm/llvm-project GitHub releases. extractVersionTemplate matches only final llvmorg-X.Y.Z tags, so -rc prereleases can never trigger a bump; only the major number is extracted (2223 when LLVM 23 ships)
  • If apt.llvm.org hasn't published packages for a new major yet, the Renovate PR's container build fails and gates the merge until they exist

Test plan

  • Full local devcontainer build with the default LLVM_VERSION=22: clang, clang-tidy, clang-format, lldb, and llvm-config all resolve to 22.1.8 via the alternatives symlinks; Valgrind 3.27.1 unaffected
  • No remaining hardcoded LLVM version references in the Dockerfile
  • renovate.json JSON validity

🤖 Generated with Claude Code

Replace the hardcoded LLVM/clang version in the Dockerfile with an
LLVM_VERSION build argument and add a Renovate regex manager that
follows llvm/llvm-project GitHub releases. The extract pattern matches
only final llvmorg-X.Y.Z tags, so release candidates never trigger a
bump; if apt.llvm.org lags a new major, the Renovate PR's container
build fails and gates the merge until packages are published.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@zeriyoshi
zeriyoshi merged commit 3569b67 into main Jul 27, 2026
2 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