ci: the mesh shard builds the TypeScript workspaces it imports
All checks were successful
CultMesh portability and performance / ubuntu-latest cache owners (pull_request) Successful in 23m32s
CultMesh portability and performance / ubuntu-latest mesh authority and content parity (pull_request) Successful in 21m41s
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Successful in 16m44s
All checks were successful
CultMesh portability and performance / ubuntu-latest cache owners (pull_request) Successful in 23m32s
CultMesh portability and performance / ubuntu-latest mesh authority and content parity (pull_request) Successful in 21m41s
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Successful in 16m44s
Run 912's mesh shard failed after 6m56s: cultnet-ts and cultmesh-ts import cultcache-ts's built output, which the reactive shard's script used to produce earlier in the single job. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
5fb1a7a921
commit
60285f4675
1 changed files with 6 additions and 0 deletions
6
.github/workflows/cultmesh-portability.yml
vendored
6
.github/workflows/cultmesh-portability.yml
vendored
|
|
@ -187,6 +187,12 @@ jobs:
|
|||
if: matrix.shard == 'cache owners'
|
||||
run: npm run test:pack:ts
|
||||
|
||||
# The reactive shard's script builds cultcache-ts and cultnet-ts, and the packages below import their built output,
|
||||
# so this shard builds the workspaces itself instead of relying on a shard that may not have run first.
|
||||
- name: Build the TypeScript workspaces
|
||||
if: matrix.shard == 'mesh authority and content parity'
|
||||
run: npm run build:ts
|
||||
|
||||
- name: Verify the CultMesh authority rules with the TypeScript verifier
|
||||
if: matrix.shard == 'mesh authority and content parity'
|
||||
run: npm run test --workspace packages/cultnet-ts
|
||||
|
|
|
|||
Loading…
Reference in a new issue