The version 3.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of postcss-loader.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 93.333% when pulling 3e614a566ff0223f079f57706fcfebb2795228f0 on greenkeeper/postcss-loader-3.0.0 into f62a65e52b28ed0745978d39c8e420f34ac82178 on master.
Coverage remained the same at 93.333% when pulling 3e614a566ff0223f079f57706fcfebb2795228f0 on greenkeeper/postcss-loader-3.0.0 into f62a65e52b28ed0745978d39c8e420f34ac82178 on master.
Version 3.0.0 of postcss-loader was just published.
The version 3.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of postcss-loader.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v3.0.02018-08-08
Bug Fixes
meta.ast
) (f34954f)warnings
as an instance of{Error}
(8ac6fb5)ValidationError
messages (549ea08)Chores
postcss
v6.0.0...7.0.0 (dependencies
) (#375) (daa0da8)BREAKING CHANGES
node >= v6.0.0
Commits
The new version differs by 27 commits.
7647ac9
chore(release): 3.0.0
313c3c4
docs(README): update filename formatting
d6931da
refactor(Error): add
error
property checks962b1d6
refactor(options): remove
ident
from validation schema1f98aee
refactor(Warning): add
warning
property checks95de4c1
docs(LOADER): update JSDoc
ea68a42
chore(package): update
schema-utils
v0.4.5...1.0.0 (dependencies
)73a8c66
chore(ISSUE_TEMPLATE/DOCS): add template for documentation issues
70f4426
chore(ISSUE_TEMPLATE/FEATURE): add feature request template
4a0328e
chore(ISSUE_TEMPLATE/BUG): move bug reports into their own template
319d1f7
chore(PULL_REQUEST_TEMPLATE): improve format and content
bdcbef0
refactor(src): update code base with latest ES2015+ features
f34954f
fix(index): add ast version (
meta.ast
)8ac6fb5
fix(index): emit
warnings
as an instance of{Error}
2c6033b
test(Errors): remove stacktrace from snapshot
There are 27 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: