oscerd opened a new pull request, #26466:
URL: https://github.com/apache/camel/pull/26466
## Problem
SBOM regeneration only ever ran for `main`. GitHub fires the `schedule`
trigger from the **default branch only**, so the copies of
`generate-sbom-main.yml` carried on `camel-4.18.x` and `camel-4.22.x` never
fired on schedule. Their committed `camel-sbom/` files went stale —
`camel-4.18.x` was last regenerated in February 2026, and `camel-4.22.x` has
had no real regen since the branch was cut.
The `sbom` Maven profile and the committed `camel-sbom/` outputs already
exist on both LTS branches, so only the *automation* was missing.
## Fix
Replace `generate-sbom-main.yml` with a single `generate-sbom.yml` (hosted
on `main`, where the schedule actually fires) that matrixes over `main` and the
active LTS branches. Each leg:
- checks out its branch (`ref: ${{ matrix.branch }}`),
- runs `./mvnw -B -Psbom -Dquickly verify`,
- opens a regen PR back against that same branch (`base: ${{ matrix.branch
}}`),
- uses per-branch PR-branch (`regen_bot_sbom_<branch>`) and artifact names
so the matrix legs don't collide.
`fail-fast: false` keeps one branch's build failure from cancelling the
others. When an LTS line reaches EOL, drop it from the matrix.
## Notes
- The `main` leg's regen branch changes from `regen_bot_sbom` to
`regen_bot_sbom_main`; the old `regen_bot_sbom` branch becomes unused and can
be deleted.
- The now-obsolete `generate-sbom-main.yml` copies still sitting on
`camel-4.18.x` / `camel-4.22.x` are inert (their schedule can never fire) but
can be removed in a small follow-up PR to each branch.
- After merge, the whole matrix can be dry-run via **workflow_dispatch** to
confirm all three legs produce their regen PRs.
_Claude Code on behalf of oscerd_
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
