Skip to content

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

Closed
kanpov opened this issue Jan 11, 2025 · 10 comments
Closed

Publish a 0.13 prerelease #2135

kanpov opened this issue Jan 11, 2025 · 10 comments

Comments

@kanpov
Copy link

kanpov commented Jan 11, 2025

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?

@kanpov
Copy link
Author

kanpov commented Jan 16, 2025

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.

@LucioFranco
Copy link
Member

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.

@lukemauldinks
Copy link

Is there any ETA on when a 0.13 will be published?

@LucioFranco
Copy link
Member

I posted an update here (I know wrong issue 😄 ) #1943 (comment)

@LucioFranco
Copy link
Member

@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.

@dzmitry-lahoda
Copy link

dzmitry-lahoda commented Mar 5, 2025

Would be awesome to start depending on axum-core more. Seems current deps only require axum full for Router.
I can PR to 0.13 usage of axum-core?

@LucioFranco
Copy link
Member

I've posted a pre-release changelog, will be working on the final items to get a release out this week.

@milesj
Copy link

milesj commented Mar 25, 2025

I don't see the changelog anywhere, do you have a link to it?

@LucioFranco
Copy link
Member

Its actually private I guess I didn't realize the draft stays private. I will publish it once it is done. Sorry about that.

@kanpov
Copy link
Author

kanpov commented Mar 26, 2025

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.

@kanpov kanpov closed this as completed Mar 26, 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

6 participants
@milesj @dzmitry-lahoda @LucioFranco @kanpov @lukemauldinks and others