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

New Release #54

Closed
Alextopher opened this issue Jan 19, 2024 · 6 comments
Closed

New Release #54

Alextopher opened this issue Jan 19, 2024 · 6 comments

Comments

@Alextopher
Copy link
Contributor

I think now would be a good time for a 3.1.0 release.

@rakshith-ravi
Copy link

reqwest has upgraded to hyper 1.0. Perhaps this can be incorporated into the new release?

Would be happy to make a PR if required

@rakshith-ravi
Copy link

Looks like it wasn't much effort. Opened one at #56

@cycle-five
Copy link

This hasn't been touched in almost 6 months. There's a number of small maintenance things that are easy and not time consuming, but really do need to be done. I'm currently using my own fork of this for my dependent code. I will probably find time over new years break to create a forked package on crates.io if there continues to be silence here.

@max-ipinfo
Copy link
Contributor

I apologize for the delay. We have had team changes in 2024 and are now trying to catch up with the backlog, across all of our OSS projects.

We are planning to cut a release shortly after rust#60 Adding features to ipinfo to support Rustls is in.

Thank you for your patience and understanding.

@max-ipinfo
Copy link
Contributor

max-ipinfo commented Jan 2, 2025

@Alextopher @rakshith-ravi @cycle-five @aalkhodiry I've just released version 3.1.0 of our library:
https://crates.io/crates/ipinfo/3.1.0

The main change is the upgrade to reqwest v0.12, turning off default features on libraries and no longer being tied to specific patch versions of dependencies.

@max-ipinfo
Copy link
Contributor

Feel free to continue to file Github issues if you have any other feedback. While I can't promise that we will integrate every change, our hope is to improve our response latency in 2025.

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

4 participants