Repository navigation
Pin Runtime artifacts through Provider declarations - #578
Merged
Merged
Conversation
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.
Runtime releases currently require every Provider to carry Docker and microsandbox identities. Store only
source_commitand the selected adapter’s declaredartifacts, and generate Go/Python/TypeScript validation and manifest selection from those declarations. Preserve Docker config/manifest identities and microsandbox image, binary and firmware checks used by preparation and cleanup.Migration 099 rejects incompatible current or retained specifications without changing data or digests, following the existing policy that each installation stays on one release. Node state is rejected before mutation; no compatibility reader or new manifest is added.
Validation: independent blind review; 3,071 Go dependency cases (four gated Docker cases skipped), 88 focused integration cases, migration protection tests, Python installer/manifest/publication suites, client/Web checks and four browser cases, module build/vet, generated contract freshness and bilingual documentation checks. Rebase to current cutover preserves the implementation and passed focused verification. Real Provider qualification remains with the cutover integration.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.