Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of deepmerge is breaking the build 🚨 #110

Open
greenkeeper bot opened this issue May 28, 2018 · 3 comments
Open

An in-range update of deepmerge is breaking the build 🚨 #110

greenkeeper bot opened this issue May 28, 2018 · 3 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented May 28, 2018

Version 2.1.1 of deepmerge was just published.

Branch Build failing 🚨
Dependency deepmerge
Current Version 2.1.0
Type dependency

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

deepmerge 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 could not complete due to an error Details

Commits

The new version differs by 10 commits.

  • dfdb723 2.1.1
  • fa594dc Update changelog for 2.1.1
  • e878b1b Merge pull request #109 from KyleAMathews/TehShrike-patch-1
  • bd2e678 Some markdown header tweaks
  • db1f8ea Merge pull request #108 from smacpherson64/patch-1
  • 2ba4f36 Minor adjustments to readme
  • 8d6a1fe Merge pull request #107 from smacpherson64/patch-1
  • dd440fe Fixed: Minor Typo in Readme
  • e980077 Merge pull request #103 from KyleAMathews/esm-syntax
  • 767499d Rename "methods" to "api", note ESM syntax

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 28, 2018

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

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Oct 3, 2018

  • The dependency deepmerge was updated from 2.1.1 to 2.2.0.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 14 commits.

  • 1d66898 2.2.0
  • 503e7c3 Changelog for 2.2.0
  • 246205c package-lock noise
  • af971b1 Merge pull request #119 from msssk/add-typescript-defs
  • 0d8bd06 Set TS version at 2.2.2 for Partial
  • d5182ab Set TS version exactly to 2.0.0
  • b643a84 Simplify TS test
  • 1de5a17 Add TypeScript definitions and test
  • 38f03f0 Merge pull request #112 from CWSites/master
  • cb37e26 adjusting the name of legacy array merge to be more clear
  • eb824c9 making adjustments based on feedback
  • 0927ac0 adjusting general note regarding arrayMerge`
  • b030f6d clarifying overwriteMerge and legacyArrayMerge
  • 3b42132 cleaning up documentation of arrayMerge options

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Oct 3, 2018

  • The dependency deepmerge was updated from 2.2.0 to 2.2.1.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 9 commits.

  • 0f5efc8 2.2.1
  • 2dbd2f9 Fix another type test issue
  • 539c4f7 2.2.1 changelog
  • f148e65 Fix typescript test not running successfully
  • 28cf0a9 Merge pull request #121 from nataly87s/patch-1
  • 739e1a3 Failing test for bad typescript types
  • c3b770d fix test
  • 68b6c06 fix type definition
  • 91d5009 Bump tap dependency to make npm audit shut up

See the full diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants