Skip to content

Conversation

CosminPerRam
Copy link
Contributor

Mentioned adding of dependabot in #485, but @jongiddy said that:

For a library crate, isn't the effect of these version updates simply to reduce the options available to dependent crates?

i.e. previously flate2 was compatible with any version of libz-sys >= 1.1.20, but now it requires at least 1.1.22. If, for any reason, a crate needs to keep libz-sys at 1.1.20, it now has a conflict.

I tend to update crate versions only when there is a security or bug fix reason to do so.

Should a dependency be updated as quick as possible? Or only if a user has a problem with one of them (or wants to) and requests to do so? A fixed schedule (i.e. once every 6 months)?

I personally consider that a project should always try to be up to date with the latest dependencies, but the points mentioned should be taken into consideration before merging of this PR.

@Byron
Copy link
Member

Byron commented Apr 28, 2025

Thanks a lot for your help with this!

Maybe we can turn this PR into a cargo audit job, or supersede it with such a PR?

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 this pull request may close these issues.

2 participants