xxchan commented on issue #4: URL: https://github.com/apache/avro-rs/issues/4#issuecomment-2368353913
I'm not asking you to change. Just ask out of curiosity, because this (i.e., upgrade **minor/patch** versions frequently in a **lib**) isn't a usual practice in Rust ecosystem. (Just unusal, not saying it's _unreasonable_ ([ref](https://arc.net/l/quote/cazyspmx))) The more common practice is that a lib only specify a minimum version. (e.g., `tokio` specifies `bytes 1.0.0` (the latest is `1.7.2`) https://github.com/tokio-rs/tokio/blob/542197cdb9031384b05ab81b64c6b6dc057a3dfc/tokio/Cargo.toml#L94). The downstream project can choose freely any sem-ver compatible versions. > What kind of problems did you have with the up-to-date transitive dependencies of avro-rs ? Any real issues ? One problem is to force downstream project to upgrade all the transitive dependencies. e.g., when I want to upgrade avro-rs, I not only need to audit changes of avro-rs, but also audit serde, anyhow, ... Because these transitive dependencies might be direct dependencies of my project, and I want to know what's changed to avoid surprise. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
