Repository navigation
build: pin published Core v0.0.10 - #70
Merged
Merged
Conversation
Replace the pre-merge pseudo-version with the tree-equivalent published release and document the current batch and receipt profiles. Standalone and cross-repository tests, vet and build pass. Co-authored-by: Codex <codex@openai.com>
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.
Pin the runtime to published Core v0.0.10 instead of its pre-merge pseudo-version. The previous Core commit and the released tag have identical complete source trees; this makes the dependency reproducible through the formal release without changing runtime behavior. Update the migration note and batch/receipt profile names accordingly.
Validation: standalone full tests, vet and build passed with GOWORK=off. The selected released Core/runtime/Gateway/evaluator workspace also passed each module's full tests, vet and build, the 292-path migration audit, and all 15 parity vectors. A fresh independent review reported no actionable findings.