Merged
Conversation
Signed-off-by: Nico Burns <nico@nicoburns.com>
emilio
approved these changes
Mar 16, 2026
Contributor
Author
|
@emilio When you get a chance, could you hit the publish button on this? (+ ideally |
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.
A release that includes #425 (I'm wanting to use this for value parsing in Taffy, which is currently very low dependency).
Note that
cssparser-colorv0.4 was never published (see #420). And I think it would still make sense to do so. I believe that all that should be required is to checkout commit 9339ddd which did the version bump forcssparser0.36 andcssparser-color0.4, and runcargo publish -p cssparser-color.It may make sense to align the version numbers of the
-colorand-macroscrates with the maincssparsercrate, but I have not done so in this PR.