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

Bump deepmerge from 2.2.1 to 4.2.2 #85

Closed

Conversation

dependabot-preview[bot]
Copy link
Contributor

@dependabot-preview dependabot-preview bot commented Nov 8, 2019

Bumps deepmerge from 2.2.1 to 4.2.2.

Changelog

Sourced from deepmerge's changelog.

4.2.2

  • isMergeableObject is now only called if there are two values that could be merged. a34dd4d2

4.2.1

  • Fix: falsey values can now be merged. #170

4.2.0

  • Properties are now only overwritten if they exist on the target object and are enumerable. #164

Technically this could probably be a patch release since "which properties get overwritten" wasn't documented and accidentally overwriting a built-in function or some function up the property chain would almost certainly be undesirable, but it feels like a gray area, so here we are with a feature version bump.

4.1.2

  • Rolled back #167 since Object.assign breaks ES5 support. 55067352

4.1.1

  • The options argument is no longer mutated #167

4.1.0

  • cloneUnlessOtherwiseSpecified is now exposed to the arrayMerge function #165

4.0.0

  • The main entry point in package.json is now a CommonJS module instead of a UMD module #155

3.3.0

  • Enumerable Symbol properties are now copied #151

3.2.1

  • bumping dev dependency versions to try to shut up bogus security warnings from Github/npm #149

3.2.0

3.1.0

  • typescript typing: make the all function generic #129

3.0.0

  • drop ES module build #123
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps [deepmerge](https://github.com/TehShrike/deepmerge) from 2.2.1 to 4.2.2.
- [Release notes](https://github.com/TehShrike/deepmerge/releases)
- [Changelog](https://github.com/TehShrike/deepmerge/blob/master/changelog.md)
- [Commits](TehShrike/deepmerge@v2.2.1...v4.2.2)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Nov 8, 2019
@github-actions
Copy link

github-actions bot commented Nov 8, 2019

Pull Request Test Coverage Report for Build c7c4882f633a60c1918be2bc198bc996f56c5256-PR-85

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 45.95%

Totals Coverage Status
Change from base Build 2ddb37c0bfcc664a2917e4913a2548c5763e549e: 0.0%
Covered Lines: 241
Relevant Lines: 398

💛 - Coveralls

@dependabot-preview
Copy link
Contributor Author

Looks like deepmerge is up-to-date now, so this is no longer needed.

@dependabot-preview dependabot-preview bot deleted the dependabot/npm_and_yarn/deepmerge-4.2.2 branch December 7, 2020 21:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants