mmintel / datocms-tools

Provides tools to import, export or reset DatoCMS projects. Will also make sure to update existing models.
10 stars 5 forks source link

An in-range update of husky is breaking the build 🚨 #20

Open greenkeeper[bot] opened 4 years ago

greenkeeper[bot] commented 4 years ago

☝️ Important announcement: Greenkeeper will be saying goodbye πŸ‘‹ and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The devDependency husky was updated from 4.2.3 to 4.2.4.

🚨 View failing branch.

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

husky 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 - ❌ **Travis CI - Branch:** The build **failed**.

Release Notes for v4.2.4
  • When Node version is unsupported, log actual version in addition to the error message #701
  • Fix: support cnpm package manager #687
  • Fix: always use sh to run scripts and avoid inconsistencies #707
  • Fix: don't throw error if files are already removed during uninstall #708
Commits

The new version differs by 8 commits.

  • 17c012d 4.2.4
  • b1d4c32 Don't throw error during uninstall if file doesn't exist (#708)
  • 4e1d440 fix: cnpm fails due to $packgeManager not matched (#687)
  • 56c611d Fix usage of SHELL environment variable can cause unexpected behavior #683
  • cbacd2e npm audit fix
  • 8bb9911 Show runtime node version when exit (#701)
  • 1bddecd Bump acorn from 5.7.3 to 5.7.4 (#688)
  • 1f7d02d Update CHANGELOG.md

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 4 years ago

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

greenkeeper[bot] commented 4 years ago

Your tests are still failing with this version. Compare changes

Release Notes for v4.2.5
  • Fix wrong error message #709
  • Update dependencies #710
Commits

The new version differs by 4 commits.

See the full diff