Problem
The LLVM_COMMIT ARG in the Dockerfile must be manually updated whenever a new llvm-project commit is needed. While the repository_dispatch path (llvm-stage1-release) overrides this at build time via --build-arg, the default value in the Dockerfile goes stale — breaking manual builds, push-to-main triggers, and workflow_dispatch runs.
Proposed Solution
Add a workflow (or extend nanvix-release.yml in llvm-project) that automatically opens a PR to bump LLVM_COMMIT in this repo's Dockerfile after each successful llvm-project release. Options:
- Dependabot-style workflow in this repo: triggered by
repository_dispatch from llvm-project, runs sed to update the commit SHA, commits, and opens a PR.
- Dispatch payload auto-commit: on
llvm-stage1-release dispatch, a pre-build step updates the Dockerfile default and pushes directly to main (simpler but less reviewable).
- Renovate/Dependabot custom datasource for git commit pinning.
Context
Problem
The
LLVM_COMMITARG in the Dockerfile must be manually updated whenever a new llvm-project commit is needed. While therepository_dispatchpath (llvm-stage1-release) overrides this at build time via--build-arg, the default value in the Dockerfile goes stale — breaking manual builds,push-to-main triggers, andworkflow_dispatchruns.Proposed Solution
Add a workflow (or extend
nanvix-release.ymlin llvm-project) that automatically opens a PR to bumpLLVM_COMMITin this repo's Dockerfile after each successful llvm-project release. Options:repository_dispatchfrom llvm-project, runssedto update the commit SHA, commits, and opens a PR.llvm-stage1-releasedispatch, a pre-build step updates the Dockerfile default and pushes directly tomain(simpler but less reviewable).Context
BINUTILS_COMMITandNEWLIB_COMMITargs