Skip to content

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

@greenkeeper

Description

@greenkeeper

Version 2.11.0 of postcss-cssnext just got published.

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

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

postcss-cssnext is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • coverage/coveralls Coverage pending from Coveralls.io 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 🌴

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions