Repository navigation
Prepare Vyral 0.3.4 and repair packaged Python upgrade qualification - #156
Merged
Merged
Conversation
jeremydixon22
changed the title
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.
The packaged Python upgrade qualification rejected the published runtime filename, assumed every baseline needed schema migration, and tried to read diagnostics from the deliberately redacted public endpoint. Accept current and legacy runtime filenames with the existing HTTPS/hash/size controls. Read the seeded baseline ledger independently and observe the installed standard CLI factory through an owner-local receipt; require the exact migration or preservation decision and keep public readiness diagnostics redacted.
Prepare general release v0.3.4 with Vyral.Abstractions and Vyral.Local 0.3.4 and prototype Python runtime 0.1.4. Attach JavaScript and lightweight Python HTTP SDK 0.3.4 archives to GitHub. npm registry delivery is deferred until trusted-publisher setup is available. The signed preparatory v0.3.3 tag has no registry or GitHub release. Wire contracts remain 0.3.0; execution packages, maturity classifications and the existing server-v0.3.6 image remain unchanged.
Validation: actual published 0.1.3 wheel upgraded successfully to 0.1.4 with authentication, persisted records/canonical data/objects/traces/execution, MCP, writes, restart and SQLite integrity checks. Schema 1 and its original migration metadata were preserved; public diagnostics remained redacted. Six fetch controls passed. Python wheel/sdist bytes match the deployment lock. Version, publication, SDK/schema and private-policy public export checks pass. Final canonical and nine-platform/host/upgrade qualification runs are required before publication.