donejs / done-ssr

Server Side Rendering for DoneJS
https://www.npmjs.com/package/done-ssr
MIT License
23 stars 11 forks source link

An in-range update of can-define is breaking the build 🚨 #676

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency can-define was updated from 2.7.14 to 2.7.15.

🚨 View failing branch.

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

can-define 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 - ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/donejs/done-ssr/builds/538948311?utm_source=github_status&utm_medium=notification)).

Commits

The new version differs by 12 commits.

  • 47137aa 2.7.15
  • b84dfc3 Merge pull request #454 from canjs/safe-mutation-check
  • ea13ae4 Upgrade tests to use QUnit 2
  • 230dc1b Merge branch 'master' into safe-mutation-check
  • 1914ebb Remove can-observation reference as the test that was using it was removed
  • 7f0d53d Clarify unsafe mutation warning in can-define regarding the value() behavior
  • 9cc835b Use full function naming for Travis job to work correctly
  • 2d89ba8 Clean up changed package refs.
  • ce0ebb7 Make the warning message for unsafe mutations more informative
  • 8530844 Dev-only tests for warnings
  • fe4726e placate linter
  • c020777 Use canSafelyMutate to generate a dev warning when setting during a getter

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

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Release Notes for Trying to set a getter that doesn't take `lastSet` throws an unhelpful error

#367

Commits

The new version differs by 3 commits.

  • db0b41c 2.7.16
  • da6574c Merge pull request #460 from canjs/357-getter-unhelpful-error
  • 9cf71af error message fixes

See the full diff

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 4 commits.

See the full diff

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 3 commits.

  • 8800be6 2.7.18
  • 1d3d2a3 Merge pull request #463 from canjs/461-failing-test-ie11-2
  • 8fcc406 ie11 more regex fixes

See the full diff