canjs / can-map-backup

Backup and restore a Maps state
https://v3.canjs.com/doc/can-map-backup.html
MIT License
2 stars 1 forks source link

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

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 3.1.1 of can-map-define just got published.

Branch Build failing 🚨
Dependency can-map-define
Current Version 3.1.0
Type devDependency

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

As can-map-define 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 failed [Details](https://travis-ci.org/canjs/can-map-backup/builds/249741477?utm_source=github_status&utm_medium=notification)

Release Notes Undeprecated Array

This patch release is a purely internal change to use Array.isArray instead of can-util/js/is-array/is-array which is now deprecated.

Commits

The new version differs by 8 commits.

  • f2995d5 Update dist for release
  • b401cc7 Merge pull request #35 from canjs/greenkeeper/initial
  • c4e2323 Merge pull request #37 from canjs/real-is-array
  • 7d4ed41 Merge branch 'master' into greenkeeper/initial
  • 294ede9 Lock down Firefix version for Travis
  • 105f1c8 Replace deprecated can-util/js/is-array with Array.isArray
  • af15d99 docs(readme): add Greenkeeper badge
  • 4fa4721 chore(package): update dependencies

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