search

webhintio / webhintio.github.io

🌍 webhint's website
https://webhint.io
Apache License 2.0
144 stars 72 forks source link

An in-range update of applicationinsights is breaking the build 🚨 #540

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency applicationinsights was updated from 1.0.5 to 1.0.6.

🚨 View failing branch.

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

applicationinsights is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/webhintio/webhint.io/builds/442399166?utm_source=github_status&utm_medium=notification)).
Release Notes for 1.0.6
  • #438 Fix spawned PowerShell processes hanging on Windows 7
  • #437 Fix infinite ACL related PowerShell processes spawning if one hangs
  • #371, #428 Fix nested custom properties report as [object Object], null/undefined property values are dropped
Commits

The new version differs by 9 commits.

  • de8679a Merge pull request #442 from Microsoft/develop
  • 818332f Bump package.json for 1.0.6 (#441)
  • d802bfc Fix timezone specific unit tests (#440)
  • da57f56 Fix powershell related bugs in Windows 7 (#439)
  • 773958d Merge pull request #428 from willmorgan/patch-1
  • c0d5e5b Skip functions from trace properties
  • 0b69674 Better handle trace obj/arr/err; allow toJSON
  • 95dabb8 Update tests to convert null/undefined to ""
  • e14b0ba Convert null, undefined props to empty strings

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 5 years ago

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