Skip to content

ci: fractional platform validation and exact-SHA release preflight #390

ci: fractional platform validation and exact-SHA release preflight

ci: fractional platform validation and exact-SHA release preflight #390

Triggered via pull request September 23, 2026 13:36
Status Success
Total duration 10m 52s
Artifacts –
Fit to window
Zoom out
Zoom in

Annotations

3 warnings and 1 notice
call / integration-test
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, astral-sh/setup-uv@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
call / integration-test
soldr cook prebuilt dependencies, but this job's compile cache recorded 524 miss(es) and 0 hit(s) — none of the cooked artifacts were reused. This usually means the job compiled under a different rust toolchain or profile than setup-soldr's cook (for example a nightly dylint/driver pass). cook cannot warm a different-toolchain compile; rely on the build-cache layer there, or set prebuild-deps: none to skip the unused cook.
call / integration-test
setup-soldr: build-cache cache payload is 2.13GB before compression (>512.0MB). Largest files: zccache/private/soldr-dev-c6a7644c722fa6b5/artifacts/81437fd86200f938d645c15dccab2faa497108e24e49b96e55f67644b3c9414d_0 (36.0MB), zccache/private/soldr-dev-c6a7644c722fa6b5/artifacts/50d44c0cda002c23f06a59d7e41c83cbb5045faa00e7d98ad9ff0ae800635d0e_0 (31.3MB), zccache/private/soldr-dev-c6a7644c722fa6b5/artifacts/a5d98227b008e34a804767ac8582e7ed85fc928482f65b6b2a10c190822e2ff2_0 (29.5MB), zccache/private/soldr-dev-c6a7644c722fa6b5/artifacts/58e003e0edf0d617b8d6af05f664aed18b68b4ce9b7a496c74288cb7df3f0f11_0 (27.4MB), zccache/private/soldr-dev-c6a7644c722fa6b5/artifacts/166a456fef3e9911330952574c49afe1915203dd9b952ed4e370384d62f8ccd2_0 (26.1MB)
call / integration-test
setup-soldr: target/ already has compiled artifacts (from `soldr cook`). target-cache is disabled, so this is the current run's own output and is expected - no action needed. (Enable target-cache and you'd get the stale-rust-plan warning instead.)