Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make cargo dependencies less specific #699

Closed
Tracked by #700
webern opened this issue Nov 3, 2023 · 0 comments · Fixed by #701
Closed
Tracked by #700

make cargo dependencies less specific #699

webern opened this issue Nov 3, 2023 · 0 comments · Fixed by #701
Assignees

Comments

@webern
Copy link
Contributor

webern commented Nov 3, 2023

          Can you reduce the specificity of the dependency versions? We have seen conflicts with other downstream dependencies at times when they require a "no-higher-than X" version.
async-recursion = "1"
async-trait = "0.1"
bytes = "1"
chrono = { version = "0.4", default-features = false, features = ["std", "alloc", "serde", "clock"] }
dyn-clone = "1"
futures = "0.3"
futures-core = "0.3"

Originally posted by @webern in #687 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant