Update fluent-uri to 0.4.1 - #811
Merged
Merged
Conversation
Shnatsel
approved these changes
Dec 8, 2025
Shnatsel
left a comment
Shnatsel
left a comment
Contributor
There was a problem hiding this comment.
Looks good to me, thank you!
To clear DCO job in CI, please click it and run the commands it specifies. Sadly I cannot merge until then.
Signed-off-by: Benjamin A. Beasley <code@musicinmybrain.net>
Signed-off-by: Benjamin A. Beasley <code@musicinmybrain.net>
Signed-off-by: Benjamin A. Beasley <code@musicinmybrain.net>
musicinmybrain
force-pushed
the
fluent-uri-0.4
branch
from
December 8, 2025 10:53
7a4d79f to
d5e55f8
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Release notes: https://github.com/yescallop/fluent-uri-rs/releases
I did this in several commits, each updating across a SemVer boundary.
The only source-code change that seemed to be required was for the renaming of
UritoUriRefin fluent-uri 0.2.0; aUriwas reintroduced in 0.3.0, but with different semantics. See yescallop/fluent-uri-rs#19 for details on this, and note that I didn’t try to evaluate whether the original semantics were the desired ones in context, only update the dependency while preserving behavior.