search

satya164 / quik

:rocket: A quick way to prototype and build apps with React and Babel with zero-setup.
525 stars 30 forks source link

An in-range update of sass-loader is breaking the build 🚨 #298

Open greenkeeper[bot] opened 7 years ago

greenkeeper[bot] commented 7 years ago

Version 6.0.6 of sass-loader just got published.

Branch Build failing 🚨
Dependency sass-loader
Current Version 6.0.5
Type dependency

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

sass-loader 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 :muscle:

Status Details - ✅ **dependency-ci** Dependencies checked [Details](https://dependencyci.com/builds/233727) - ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/satya164/quik/builds/243062124?utm_source=github_status&utm_medium=notification)
Commits

The new version differs by 9 commits.

  • a1ae204 chore: Update changelog for 6.0.6
  • aed60eb chore(release): 6.0.6
  • 85d7772 chore: Adds release script
  • 43199f1 chore: Reformat changelog for standard-version
  • 5daa32b chore(package): Adds contrib standard release tooling
  • 0511c25 chore: build and package updates to allow use of webpack 3 (#475)
  • 0d6d66d refactor: remove this.cacheable (#473)
  • 876876a docs(readme): Fixes typo in loader description (#472)
  • c27063c chore(package): update dependencies (#470)

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:

greenkeeper[bot] commented 7 years ago

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