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

Unpin Major Crate Deps #327

Open
j-mendez opened this issue Jan 29, 2025 · 0 comments
Open

Unpin Major Crate Deps #327

j-mendez opened this issue Jan 29, 2025 · 0 comments

Comments

@j-mendez
Copy link

Hello,

I wanted to bring up the idea of unpinning major dependencies. Upon comparing the latest releases, I noticed that version 0.27 is approximately 5 MB smaller than 0.26. This observation led me to question the overall size of the crate, primarily due to our major dependencies that might be commonly used across different projects.

By unpinning these major dependencies, we can allow users to utilize compatible versions available in their projects, potentially reducing the crate's size and optimizing resource usage. Of course, if a specific version of a dependency is crucial due to known bugs or other critical issues, it would make sense to keep it pinned.

For example, instead of pinning reqwest to v0.12.12, we could consider unpinning it to allow for any v0.12.x version. Given the nature of libraries like reqwest, it may not be necessary to pin each version for rigorous testing.

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

No branches or pull requests

1 participant