search

googlearchive / npm-publish-scripts

Some shell scripts and a Jekyll + JSDoc theme pair to help publish NPM projects with documentation.
https://googlechrome.github.io/npm-publish-scripts/
Apache License 2.0
40 stars 15 forks source link

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

Open greenkeeper[bot] opened 7 years ago

greenkeeper[bot] commented 7 years ago

Version 6.4.0 of gulp-postcss just got published.

Branch Build failing 🚨
Dependency gulp-postcss
Current Version 6.3.0
Type devDependency

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

As gulp-postcss 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 :muscle:

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/GoogleChrome/npm-publish-scripts/builds/213114923)
Release Notes 6.4.0
  • Add more details to PluginError object
Commits

The new version differs by 10 commits .

  • 0ab5177 Release 6.4.0
  • 343d410 Merge pull request #101 from gucong3000/error_details
  • e572833 Merge pull request #110 from michael-ciniawsky/master
  • 18e02da Update postcss-load-config v1.1.0...1.2.0
  • f7535b8 Merge branch 'master' into error_details
  • fe8e5f5 update test case
  • 44e7d88 Modify, according to @W0rm ‘s opinion
  • d765342 Merge branch 'master' into error_details
  • 7f9253c use es5 syntax
  • 28d5ec1 pass CssSyntaxError and Error details to gutil.PluginError

See the full diff.

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree: