Update postcss-modules-values to version 1.2.2 🚀 #153
Merged
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
geelen
force-pushed
the
greenkeeper-postcss-modules-values-1.2.2
branch
from
98aa66e to
6904eac
Compare
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-modules-values just published its new version 1.2.2.
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-modules-values.
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!
🌴
The new version differs by 26 commits .
a153e671.2.276c1ed2restored babel 5 exports3506ce51.2.1a67db17dont ignore lib dir for npm, only git6265c29Merge branch 'alexanderchr-master'34d48e2Merge branch 'master' of https://github.com/alexanderchr/postcss-modules-values into alexanderchr-master75e065c1.2.0657d2b4Merge branch 'tec27-comma_defs'd9970d1Merge branch 'comma_defs' of https://github.com/tec27/postcss-modules-values into tec27-comma_defsb1594ebMerge pull request #60 from css-modules/pveyes-dependency_update6da5150Merge branch 'dependency_update' of https://github.com/pveyes/postcss-modules-values into pveyes-dependency_update56bf40aMerge pull request #36 from css-modules/greenkeeper-babel-6.5.267444c1Merge pull request #44 from cbracco/patch-15134ef4chore(package): update babel to version 6.5.25af4129Merge pull request #50 from css-modules/greenkeeper-standard-7.1.2There are 26 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade