Repository navigation
Accept stable runtime compatibility lines - #57
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.
Core now accepts stable repository versions in its runtime's compatibility line: minor versions before 1.0 and major versions from 1.0 onward. Hosted event previews and saves can use one tested patch in that line without rewriting customer package manifests, lockfiles, or workspace versions.
A shared compatibility result exposes installed and repository versions, supported line, model and API support, and a failure reason. CLI, evaluations, previews, server startup, and mutation guards use it. Malformed versions, prereleases, unsupported lines/contracts/models, unresolved links, and missing managed lockfiles remain rejected. Model diagnostic views and explicit migrations preserve recovery access while ordinary writes remain blocked. Previews use current dependency metadata alongside current records.
Validation: fresh Node 24
CI=true npm run validate; 43 focused tests; browser event saves against a 0.17.2 lock, malformed-model recovery reads and rejected writes, clean console/network; published 0.17.0/current event and generated-task interchange on models 2 and 12; fresh consumer with 224 records and no errors/warnings; both package dry runs; npm audit and private-source/secret scans. Independent code/security review is clean.Coordinated patch release 0.17.4. No migration is required. Previously published runtimes keep their old exact-version guard, so hosted deployments must upgrade their runtime to adopt this policy.