Commit bae1642
committed
fix(ci): bump rust-target cache volume to unstick the plugin runtime
The wasm32-wasip2 fix (20368ff) didn't take: the Pets E2E run on
that exact commit still failed with the identical "this server was
built without the plugin runtime" 500. build.rs's build_plugin_runtime()
only declares `rerun-if-changed` on plugin-runtime/{src,wit} and the
ATOMICSERVER_SKIP_PLUGIN_RUNTIME env var — nothing tells cargo that
"the wasm32-wasip2 target just became installed" should invalidate its
build-script fingerprint. Every prior CI run had already cached an
empty embedded runtime (from before that target existed) in the
rust-target-v3 volume, so cargo kept trusting that stale fingerprint
and never re-ran the nested wasm32-wasip2 build to notice the target
was now there.
This is the same class of staleness bug TOUCH_WORKSPACE_SOURCES
already documents fixing twice before (the -v2 and -v3 renames on this
same volume, for the same "cached artifact looks newer than fresh
sources" reason) — same fix, one more rename to force a clean
re-evaluation.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KkL48idFqkuYw8n7KdH6Dj1 parent 6acc3fa commit bae1642
1 file changed
Lines changed: 11 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1162 | 1162 | | |
1163 | 1163 | | |
1164 | 1164 | | |
1165 | | - | |
| 1165 | + | |
| 1166 | + | |
| 1167 | + | |
| 1168 | + | |
| 1169 | + | |
| 1170 | + | |
| 1171 | + | |
| 1172 | + | |
| 1173 | + | |
| 1174 | + | |
| 1175 | + | |
1166 | 1176 | | |
1167 | 1177 | | |
1168 | 1178 | | |
| |||
0 commit comments