Skip to content

ci: register build accelerator routing - #1872

Merged
i386 merged 1 commit into
mainfrom
scama/build-defaults-catalog
Sep 14, 2026
Merged

i386 merged 1 commit into
mainfrom
scama/build-defaults-catalog

Conversation

@i386

@i386 i386 commented Sep 14, 2026

Copy link
Copy Markdown
Collaborator

The protected PR planner requires ci/ownership.yml and ci/slices.yml to match the default branch byte for byte. This prerequisite publishes the routing data needed by #1870 so that the feature branch can be rebased and validated.

  • register the Windows short-path action under the Windows platform domain
  • repin the four Linux runtime rows to the promoted mold/sccache runner cohort

This is the repository's documented sequenced-maintainer-merge path for catalog evolution. The catalog PR's own Plan checks are expected to reject the source/default mismatch until it lands.

Validation: 53 planner/lane contract tests passed; just ci-crate-lists passed.

Summary by CodeRabbit

  • Chores
    • Expanded automated ownership coverage for Windows-related setup workflows.
    • Refreshed Linux build and validation environments across CPU, CUDA, ROCm, and Vulkan configurations.
    • Updated toolchain and environment versions used during automated checks to keep platform validation consistent.

@coderabbitai

coderabbitai Bot commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

Review Change StackReview Change Stack

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: b437b38b-6a61-4ed1-a658-0c589e4d1d95

📥 Commits

Reviewing files that changed from the base of the PR and between 9c40125 and 2c6a8e7.

📒 Files selected for processing (2)
  • ci/ownership.yml
  • ci/slices.yml

📝 Walkthrough

Walkthrough

The pull request updates Windows ownership patterns and refreshes container image digests and toolchain epochs for four Linux runtime rows.

Changes

Windows ownership routing

Layer / File(s) Summary
Windows path ownership routing
ci/ownership.yml
The platform-windows domain now matches .github/actions/setup-windows-short-paths/**.

Linux runtime metadata

Layer / File(s) Summary
Linux runtime image pins
ci/slices.yml
The linux-cpu, linux-cuda, linux-rocm, and linux-vulkan rows now use updated container_image digests and matching toolchain_epoch values.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Feature

Suggested reviewers: ndizazzo

✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch scama/build-defaults-catalog

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@i386
i386 merged commit dde0af8 into main Sep 14, 2026
1 of 7 checks passed
@i386
i386 deleted the scama/build-defaults-catalog branch September 14, 2026 22:11
i386 pushed a commit that referenced this pull request Sep 15, 2026
Move the promoted runner catalog and every matching workflow binding into the prerequisite that provisions sccache for protected Quality jobs. This repairs the transitional planner/catalog drift left after #1872 and keeps the release and runtime-seed contracts aligned with the promoted cohort.

Validation: just ci-validate components pass, including 1,474 tests with 9 skipped; runner identity reports 9 images, 35 roles, and 36 bindings.
i386 added a commit that referenced this pull request Sep 15, 2026
# Problem

PR #1872 moved the protected planner's four Linux runtime rows to the
promoted runner cohort, while `ci/runner-images.json` and the remaining
workflow bindings still described the previous cohort. That transitional
split makes repository identity checks fail on `main`. Separately, the
protected Quality workflow did not provision sccache before Cargo
invocations, which blocks PR #1870 once the repository-level
`rustc-wrapper` becomes mandatory.

# Result

This prerequisite completes the promoted-image transition before #1870:

- admits the promoted nine-image cohort with its retained promotion
receipt;
- updates all 36 registered workflow bindings and their toolchain
epochs;
- gives crates.io publish and resume jobs the registered CPU container
and local sccache policy;
- rotates compiler-seed identity for the new CPU image and prevents
branch cache shadowing;
- provisions sccache in both protected Quality jobs;
- updates the matching catalog, release, cache, and artifact contracts.

The linker defaults and Windows short-path build behavior remain in
#1870. After this lands, #1870 can rebase onto a consistent protected
planner/catalog base.

# Validation

On exact head `b453d87f289ba71631a33e42f67162dcae5a4f01`:

- `just ci-validate`: passed, including 1,474 tests with 9 skipped;
- runner image identity: 9 images, 35 roles, 36 workflow bindings, 4
runtime rows, 6 seed consumers;
- actionlint and `git diff --check`: passed;
- release targets, crate-list consistency, console-print policy, and
publish-chain consistency: passed.


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Chores**
* Updated build, test, and release workflows to newer verified runner
images.
* Refreshed cache keys and expanded caching configuration across CI and
release workflows.
  * Added provenance and receipt details for runner images.
* Added dedicated release publishing environments with safer cache
settings and checkout validation.
  * Restricted runtime seed canary execution to the main branch.

* **Tests**
* Expanded validation for runner image provenance, cache identity,
release workflows, and canary behavior.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: scama <a1860575018c4680d5669dd7bc3bd356b478bccb8d42e194df46304a5e25f49a@meshllm.communities.buzz.xyz>
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