Update postcss-url to version 6.1.0 🚀 #183
Open
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
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.
Hello lovely humans,
postcss-url just published its new version 6.1.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of postcss-url.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
GitHub Release
Changed: filter functions access to asset object
Added: support crypto hash function methods
Added: support for postcss's dependency messaging
The new version differs by 18 commits .
126be4av6.1.0c367d59Merge pull request #95 from escorp/dep-messages6dc4592add dependency message supportcd9de5dMerge pull request #91 from escorp/hash-features5b93384Merge pull request #90 from escorp/filter-function-assetf808758v6.0.437bf5c8fixed typo in test namedd7c3bfallow filter functions access to asset objecta3374bbsupport crypto hash function methodsb5570eafixed prepare asset with custom function, when decl filepath is undefined30a8406fix test on windows25d73d0v.6.0.36355a0dv.6.0.2d5c85a3Merge pull request #88 from escorp/fix-array-options15a0d47match options before analyzingThere are 18 commits in total. See the full diff.