Repository navigation
feat: simplify SDK ownership and publish 0.69 on crates.io - #529
Merged
Merged
Conversation
Signed-off-by: jbernavaprah <webjure@gmail.com>
Signed-off-by: jbernavaprah <webjure@gmail.com>
Signed-off-by: jbernavaprah <webjure@gmail.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
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.
The SDK now owns reusable runtime and protocol contracts, authoring macros, and local build generation. Applications and official participant implementations have independent repositories. Production wire protocols use the Phoxal Rust message authoring path with standard Protobuf descriptors and independent reference conformance tests.
This release restores ordinary crates.io distribution at 0.69.0 and replaces custom registry publication with standard release-plz jobs. Authored robot sources use local paths or pinned Git. Prepared contract reading and writing now share phoxal-build: the writer owns serialization, publication locks, coherent pair replacement, interruption recovery, and unchanged-content handling. Implementation-only rebuilds preserve bindings. Package versions do not determine application compatibility.
Validation: SDK library and deterministic tests, supported consumer profiles, independent Protobuf conformance, generated API fixtures, warm-edit regression, doctests, strict Clippy and rustdoc, formatting, and build-helper package verification passed locally. Remote CI must pass before delivery. Dependent applications still require the public 0.69.0 packages before their final registry-backed installation and runtime qualification.