Skip to content

Conversation

jplatte
Copy link
Member

@jplatte jplatte commented Mar 27, 2025

Release log (to be done post merge):

  • Run cargo publish in the right order
  • Create git tags
  • Create GitHub releases

@jplatte jplatte requested a review from mladedav March 27, 2025 14:58
@jplatte jplatte marked this pull request as draft March 27, 2025 16:35
@jplatte
Copy link
Member Author

jplatte commented Mar 27, 2025

Switching to draft because I want #3294 to land first, and I want to include axum-extra as well now that it's no longer going to be a breaking change.

@jplatte jplatte marked this pull request as ready for review March 28, 2025 10:18
@jplatte jplatte changed the title Release axum-core 0.5.2 and axum 0.8.3 Release axum 0.8.3 and related crates Mar 28, 2025
Copy link
Collaborator

@mladedav mladedav left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we also release axum-extra as 0.11.1? If someone already upgraded (and wasn't hit by the breaking change) they'll be on the yanked version until we release another version which I assume we don't plan to do ever and with the next breaking version we'll jump directly to 0.12. Re-adding the feature is not a breaking change so that should not be a problem.

Otherwise, we can just ignore that and potentially point people to using 0.10 instead of 0.11 again.

@jplatte jplatte merged commit b150ac0 into main Mar 28, 2025
18 checks passed
@jplatte jplatte deleted the jplatte/v0.8.3 branch March 28, 2025 16:26
@jplatte
Copy link
Member Author

jplatte commented Mar 28, 2025

I don't see much of a point. If it's working, no need to do anything about it.

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