-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Publish a 0.13 prerelease #2135
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
Comments
For now, I'm using a git dependency on the repo, but this is obviously restricted by the fact that no crates.io libraries can do this. |
Yeah, I will look into getting this done in the next few weeks. There are some major things coming to tonic that have slowed down the current release progress. |
Is there any ETA on when a 0.13 will be published? |
I posted an update here (I know wrong issue 😄 ) #1943 (comment) |
@tottoto I think what we have now done in the milestone is pretty good and I think we should prep a release if you want to do that otherwise I can once I am back. |
Would be awesome to start depending on axum-core more. Seems current deps only require axum full for Router. |
I've posted a pre-release changelog, will be working on the final items to get a release out this week. |
I don't see the changelog anywhere, do you have a link to it? |
Its actually private I guess I didn't realize the draft stays private. I will publish it once it is done. Sorry about that. |
0.13.0 is published, so this is fixed. But I do suggest more actively employing prereleases and releasing more often so that situations like these become rarer. |
It'd be nice to have a 0.13 prerelease available in order to address the major dependency duplication issues 0.12 has (tower, and now also axum) before 0.13 is stabilized fully. Would this be possible?
The text was updated successfully, but these errors were encountered: