Stabilize visual preview processor fingerprints - #279
Open
rodboev wants to merge 3 commits into
Open
Conversation
roborev: Combined Review (
|
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
1 participant
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.
Visual preview recipe identity now stays stable across Go toolchain-only upgrades, so the ambient runtime version no longer creates another durable generation on next access. The processor descriptor remains explicit and changes when a byte-producing implementation or policy changes.
The canonical recipe and persisted generation key keep their existing validation and immutability rules. Producer and vault tests pin both identities, and the descriptor records the linked image dependency and preview policy that affect output.
Preview head ordering, source-metadata heads, and generation cleanup remain separate work.
Refs #270