Skip to content

fix(build): validate project finalizer caches - #40

Merged
imathwy merged 1 commit into
mainfrom
fix/project-finalizer-doc-cache-layout
Sep 5, 2026
Merged

fix(build): validate project finalizer caches#40
imathwy merged 1 commit into
mainfrom
fix/project-finalizer-doc-cache-layout

Conversation

@imathwy

@imathwy imathwy commented Sep 5, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • accept the exact schema-3 per-project finalizer cache layout used by remote project jobs
  • keep writable branch/project finalizer dependencies content-hashed while preserving the immutable branch-cache fast path
  • bound and no-follow metadata reads, document the cross-SDK contract, and add legacy/configured/project regression coverage

Failure reproduced

The Algebraic Topology canary failed before doc-gen with managed Lake cache has an unsafe namespace layout; the cache copy and 12,693-artifact synchronization had succeeded and no OOM occurred.

Validation

  • capability SDK suite: pass (build 69, deploy 138, plus common/verso/graph/comparator suites)
  • repository suite: 50/50 pass
  • SiFlow suite including producer-to-consumer contract: 175/175 pass
  • Ruff, format, py_compile, bash syntax, and diff checks: pass
  • independent review: no blocker/high/medium after writable branch-finalizer handling was added

@imathwy
imathwy merged commit 8347ef7 into main Sep 5, 2026
2 checks passed
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.

2 participants