An in-range update of postcss-cssnext is breaking the build 🚨

[greenkeeper]

Version 2.11.0 of postcss-cssnext just got published.

Branch	Build failing 🚨
Dependency	postcss-cssnext
Current Version	2.10.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As postcss-cssnext is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

2.11.0

• Added: image-set() support
  (via postcss-image-set-polyfill)
  (#373 - @SuperOl3g)
• Added: new auto-deactivation rule in features map
  (#369 - @Semigradsky)

Commits

The new version differs by 10 commits0.

• ed02dc8 2.11.0
• b6f4796 Fix "Unknow browserslist" error
• 480687c Add browsers for testing new futures
• e7cb40b Merge pull request #369 from Semigradsky/patch-1
• 08dd185 Merge pull request #373 from SuperOl3g/master
• 2ca6df0 Fix failed tests.
• a1f8143 update image-set-polyfill package version
• 4c982cd Added: postcss-image-set-polyfill (#43)
• 5200ff2 Add caniuse-db as peer dependency.
• d3b21c1 Update features-activation-map

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴