Prepare new releases #516
Merged
Prepare new releases #516
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I think this will also need to update the version of markup5ever (as well as the dependency in html5ever/xml5ever) and the version of xml5ever. We need to release new versions of all three crates. |
Need semver-incompatible bump after a phf bump in markup5ever.
mrobinson
approved these changes
Mar 20, 2024
djc
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not completely sure if changes from #460 should be considered semver-incompatible? It looks like they add new states but then also the
statesmodule has these comments:So maybe it doesn't matter?
As far as I can tell other changes are not semver-incompatible.