Adopt runtime contract major 2 and verify package compatibility - #36
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.
Both exact-target clients require runtime contract major 2, use collection/instrument identifiers for the three corrected robot Machine ID parameters, and decode typed overload rejection. Standard protocol imports remain pinned to the verified 0.9.0-dev.1 server artifact because the 0.9.0-dev.2 server has identical public descriptors and compatibility coordinates.
The unpublished 0.4.0 package candidates and migration notes coordinate the server break. Package conformance distinguishes expected installation rejection from operation compatibility and records package identity separately from fixture source.
Validation: 93 unit tests, builds and static checks, verified protocol imports and package identity. Both actual 0.4.0 packages passed all 12 fake-SDK conformance scenarios against the new 0.9.0-dev.2 packaged server for their exact targets. The retained 0.2.0 and 0.3.0 packages rejected the new server at compatibility major 2. The six current and twelve older pair results are retained in the server candidate evidence. No packages have been published and no licensed-SA client coverage is claimed.
Refs #35
Refs spatialanalyzer/briosa#220