Conversation
subxt-signer depends on subxt and subxt-codegen depends on subxt-metadata, but subxt and subxt-metadata used them as versioned dev-dependencies through `workspace = true`. Packaging at a not-yet-published version then fails to resolve the cycle. Cargo drops path dev-dependencies without a version when packaging, so make these path-only. subxt-utils-stripmetadata is not a cycle but gets the same treatment for consistency.
This branch has not been deployed
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.
NOTE: the automation only starts working once
parity-crate-ownerowns all 11 crates. It currently ownssubxt,subxt-macroandsubxt-codegen, a current owner has to add it to the rest: