ci: rebuild the dependent container images on a merge - #83
Merged
Merged
Conversation
Contributor
CI report —
|
| Workflow | Result | Time | Run |
|---|---|---|---|
| Commit policy | ✅ success (steps skipped — no code changes) | 0m19s | #115 |
| E2E dApp Integration | ✅ success (steps skipped — no code changes) | 0m26s | #123 |
| E2E Topologies (multi-dApp / multi-RAN) | ✅ success (steps skipped — no code changes) | 0m28s | #121 |
| Full-loop Latency Benchmark | ✅ success (steps skipped — no code changes) | 0m20s | #122 |
| Unit Tests | ✅ success (steps skipped — no code changes) | 0m35s | #149 |
| latrec portability | ⏭️ not triggered (paths filter) | — | — |
| MPMC Queue Benchmark | ⏭️ not triggered (paths filter) | — | — |
Ready to merge (fast-forward only)
A maintainer can land the reviewed commits with:
git fetch origin
git checkout main && git merge --ff-only 152ea05f99efd5df64adaa59db8b88696ba775a8 && git push origin mainHead: 152ea05f99efd5df64adaa59db8b88696ba775a8 (branch ci/refresh-dependent-images). If --ff-only fails as non-fast-forward, the branch must be rebased on the latest main.
One comment per PR, rewritten in place once every workflow for
152ea05finished.
Thecave3
changed the title
A downstream repository builds images that bake this library's source, and a merge here left them stale: nothing asked for a rebuild. Dispatches that repository's publish workflow, pinned to this commit. The pin matters as much as the trigger -- those builds clone by branch when no pin is given, so the layer cache replays the old clone and republishes an unchanged image while reporting success. This repository is public, so the downstream repository is named by the DOWNSTREAM_IMAGE_REPO variable rather than inline, and the job fails with a clear message if it is unset. The owner comes from github.repository_owner for the same reason. Runs on a hosted runner: minutes are free for a public repository, and this one has never had access to a self-hosted runner. Authenticates with a GitHub App rather than a PAT, so the token is minted per run, expires, and is scoped to the one downstream repository. Assisted-by: Claude:claude-opus-5
Thecave3
force-pushed
the
ci/refresh-dependent-images
branch
from
September 23, 2026 12:36
a9845df to
152ea05
Compare
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
1 participant
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.
A downstream repository builds container images that bake this library's source. A merge here left those images stale, because nothing asked for a rebuild.
This dispatches that repository's publish workflow, pinned to this commit.
Those builds clone by branch when no commit pin is given. A branch name never changes between commits, so the layer cache replays the old clone and the rebuild republishes an unchanged image while reporting success. The downstream repository recently gained both the commit pins and the workflow input this passes.
Runner
ubuntu-latest. Hosted minutes are free for a public repository, and this repository has never had access to a self-hosted runner.