search

rm3web / sitepath

A self-describing URL path-like thing
1 stars 0 forks source link

An in-range update of chai is breaking the build 🚨 #46

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 7 years ago

Version 4.1.2 of chai just got published.

Branch Build failing 🚨
Dependency chai
Current Version 4.1.1
Type devDependency

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

As chai 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 could not complete due to an error [Details](https://travis-ci.org/rm3web/sitepath/builds/270628569?utm_source=github_status&utm_medium=notification)
Release Notes 4.1.2 / 2017-08-31

This release fixes a bug when running in certain environments, and includes a few minor documentation fixes.

Bug Fixes

  • fix: update deep-eql to version 3.0.0 (#1020)
  • fix: replace code causing breakage under strict CSP (#1032; @Alhadis)

Docs

Commits

The new version differs by 8 commits.

  • 529d395 Merge pull request #1037 from Cutlery-Drawer/master
  • b534fca chai@4.1.2
  • c592551 Merge pull request #1032 from Cutlery-Drawer/csp-fix
  • 31c3559 Use a hardcoded no-op instead of instancing
  • 1ae9386 Merge pull request #1025 from yanca018/master
  • 786043b Update license
  • 7c1ca16 docs: add missing assert parameters (#1023)
  • 6e72c5a fix(package): update deep-eql to version 3.0.0 (#1020)

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 4.1.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.