Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
greenkeeper bot opened this issue Jan 22, 2019 · 18 comments
Open

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

greenkeeper bot opened this issue Jan 22, 2019 · 18 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Jan 22, 2019

The devDependency postcss was updated from 7.0.13 to 7.0.14.

🚨 View failing branch.

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

postcss is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for 7.0.14
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jan 22, 2019

After pinning to 7.0.13 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 4, 2019

  • The devDependency postcss was updated from 7.0.14 to 7.0.15.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 7.0.15
  • Fix Custom Properties support (by @isolovev).

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 4, 2019

  • The devDependency postcss was updated from 7.0.15 to 7.0.16.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jun 5, 2019

  • The devDependency postcss was updated from 7.0.16 to 7.0.17.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 7.0.17

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Sep 5, 2019

  • The devDependency postcss was updated from 7.0.17 to 7.0.18.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Oct 24, 2019

  • The devDependency postcss was updated from 7.0.18 to 7.0.19.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 7.0.19
  • Fix passing nodes property to node constructor.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Oct 24, 2019

  • The devDependency postcss was updated from 7.0.19 to 7.0.20.

Your tests are still failing with this version. Compare changes

Release Notes for 7.0.20
  • Allow to pass PostCSS’s nodes in nodes property to node constructor.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Oct 25, 2019

  • The devDependency postcss was updated from 7.0.20 to 7.0.21.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Nov 19, 2019

  • The devDependency postcss was updated from 7.0.21 to 7.0.22.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 7.0.22
  • Add funding link for npm fund.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Nov 19, 2019

  • The devDependency postcss was updated from 7.0.22 to 7.0.23.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 7.0.23
  • Update Processor#version.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 6, 2019

  • The devDependency postcss was updated from 7.0.23 to 7.0.24.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 7.0.24

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 16, 2019

  • The devDependency postcss was updated from 7.0.24 to 7.0.25.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 7.0.25
  • Fix absolute path support for Windows (by @tomrav)

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Feb 18, 2020

  • The devDependency postcss was updated from 7.0.26 to 7.0.27.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 7.0.27
  • Fix TypeScript definition (by @nex3).

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 2, 2020

  • The devDependency postcss was updated from 7.0.27 to 7.0.28.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 4, 2020

  • The devDependency postcss was updated from 7.0.28 to 7.0.29.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 11, 2020

  • The devDependency postcss was updated from 7.0.29 to 7.0.30.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 26, 2020

  • The devDependency postcss was updated from 7.0.30 to 7.0.31.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 7.0.31
  • Use only the latest source map annotation (by @emzoumpo).

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jun 2, 2020

  • The devDependency postcss was updated from 7.0.31 to 7.0.32.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants