publish versions of html,xml and markup5ever with new tendril release #710
+4
−4
Conversation
This file contains hidden or 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
Signed-off-by: Simon Wülker <simon.wuelker@arcor.de>
Contributor
Wasn't that included in the 0.37.0 release? |
Contributor
|
Ah, I was not aware that we had made a release so recently (version bump was included in with another PR rather than it having a dedicated version bump PR). |
nicoburns
approved these changes
Jan 12, 2026
Member
|
This version isn't up on crates.io yet. |
Member
|
Published. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
#704 bumped tendril to 0.5 but there are no versions of markup5ever/html5ever/xml5ever using this release yet, preventing me from using it in servo. I missed this detail in the original PR.
As far as I know it is more or less an unresolved question whether bumping a dependency to a non-backwards-compatible new version should be considered a breaking change, I went with a patch release here.