refactor(producer): add plan v2 artifact publisher#2792
Open
jrusso1020 wants to merge 1 commit into
Open
Conversation
This was referenced Jul 25, 2026
Collaborator
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
jrusso1020
force-pushed
the
feat/plan-protocol-v2-gcp
branch
from
July 25, 2026 23:33
5fc20bd to
d5991e5
Compare
jrusso1020
force-pushed
the
feat/plan-v2-artifact-publisher
branch
from
July 25, 2026 23:33
b6f41f6 to
8c31919
Compare
jrusso1020
force-pushed
the
feat/plan-v2-artifact-publisher
branch
from
July 25, 2026 23:37
8c31919 to
7ecae52
Compare
jrusso1020
force-pushed
the
feat/plan-protocol-v2-gcp
branch
from
July 25, 2026 23:37
d5991e5 to
33a06aa
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

What
Introduces a manifest-last
PlanV2ArtifactPublisherseam and routesplanV2()through a local publisher. The local implementation hard-links immutable blobs when staging and CAS share a filesystem, with an atomic copy fallback for cross-device or restricted filesystems.The frozen v1 catalog and manifest construction are now storage-independent, duplicate digests publish once, and the existing synchronous
createPlanV2FromV1()compatibility helper remains available.Why
Plan v2 currently creates a complete v1 staging tree and then copies the retained bytes into a second local CAS tree before cloud upload. This PR is the first direct-emission foundation: it removes the second set of local data blocks on the normal same-filesystem path and establishes the manifest-last publisher contract needed by direct S3/GCS emission.
This does not yet remove the complete v1 staging tree. That remains the next stacked producer change; oversized-plan rollout stays disabled.
How
plan.jsonTest plan