Repository navigation
Prepare Open Crate packages for crates.io - #1
Merged
Merged
Conversation
AlexiAxAxA
marked this pull request as ready for review
September 23, 2026 06:23
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.
Purpose
Prepare the five Open Crate libraries and a thin
opencratefacade for a coordinated crates.io release. The facade lets consumers use one dependency; individualoc-*packages remain available.Changes
opencratere-exports for the five libraries.Validation
cargo check --locked --workspace --offlinepassed.cargo publish -p oc-policy --dry-runandcargo publish -p oc-crypto --dry-runpassed; neither uploaded.Remaining release gates
oc-policy,oc-crypto,oc-format,oc-protocol,oc-engine,opencrate. Verify each dependent package after its dependencies appear in the registry.This PR does not publish a crate.