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 lodash and bitcore-lib #12

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Apr 25, 2023

Bumps lodash to 4.17.21 and updates ancestor dependency bitcore-lib. These dependencies need to be updated together.

Updates lodash from 3.10.1 to 4.17.21

Release notes

Sourced from lodash's releases.

4.0.0

lodash v4.0.0

2015 was big year! Lodash became the most depended on npm package, passed 1 billion downloads, & its v3 release saw massive adoption!

The year was also one of collaboration, as discussions began on merging Lodash & Underscore. Much of Lodash v4 is proofing out the ideas from those discussions. Lodash v4 would not be possible without the collaboration & contributions of the Underscore core team. In the spirit of merging our teams have blended with several members contributing to both libraries.

For 2016 & lodash v4.0.0 we wanted to cut loose, push forward, & take things up a notch!

Modern only

With v4 we’re breaking free from old projects, old environments, & dropping old IE < 9 support!

4 kB Core

Lodash’s kitchen-sink size will continue to grow as new methods & functionality are added. However, we now offer a 4 kB (gzipped) core build that’s compatible with Backbone v1.2.4 for folks who want Lodash without lugging around the kitchen sink.

More ES6

We’ve continued to embrace ES6 with methods like _.isSymbol, added support for cloning & comparing array buffers, maps, sets, & symbols, converting iterators to arrays, & iterable _(…).

In addition, we’ve published an es-build & pulled babel-plugin-lodash into core to make tree-shaking a breeze.

More Modular

Pop quiz! 📣

What category path does the bindAll method belong to? Is it

A) require('lodash/function/bindAll') B) require('lodash/utility/bindAll') C) require('lodash/util/bindAll')

Don’t know? Well, with v4 it doesn’t matter because now module paths are as simple as

var bindAll = require('lodash/bindAll');

We’ve also reduced module complexity making it easier to create smaller bundles. This has helped Lodash adoption with libraries like Async & Redux!

1st Class FP

With v3 we introduced lodash-fp. We learned a lot & with v4 we decided to pull it into core.

Now you can get immutable, auto-curried, iteratee-first, data-last methods as simply as

var _ = require('lodash/fp');
var object = { 'a': 1 };
</tr></table> 

... (truncated)

Commits
  • f299b52 Bump to v4.17.21
  • c4847eb Improve performance of toNumber, trim and trimEnd on large input strings
  • 3469357 Prevent command injection through _.template's variable option
  • ded9bc6 Bump to v4.17.20.
  • 63150ef Documentation fixes.
  • 00f0f62 test.js: Remove trailing comma.
  • 846e434 Temporarily use a custom fork of lodash-cli.
  • 5d046f3 Re-enable Travis tests on 4.17 branch.
  • aa816b3 Remove /npm-package.
  • d7fbc52 Bump to v4.17.19
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by bnjmnt4n, a new releaser for lodash since your current version.


Updates bitcore-lib from 0.13.19 to 10.0.5

Release notes

Sourced from bitcore-lib's releases.

v8.22.2

No release notes provided.

v8.16.2

No release notes provided.

v8.2.0

No release notes provided.

v8.1.0

All notable changes to this project will be documented in this file. See Conventional Commits for commit guidelines.

8.1.0 (2019-02-27)

Bug Fixes

  • do not remove scripts from outputs (0d9dc85)
  • failed verification if customData is object (1848cd5)
  • Fix callback name (44a45de)
  • fix variable typo for paypro. (6db7923)
  • handle outgoing TXs foreign crafted (869840e)
  • show message unconfirmed transactions if there is not transaction confirmed yet (aea2af5)
  • node: fix test (06dee24)
  • show tx without input addres. Show type of address for tx out (fb00366)
  • bitcore-node: set all indexes to build in the background (107fe0b)
  • lib-cash: match bitcore-lib estimateFee fix (8650345)
  • node: config and rate limit (d352b20)
  • node: config properties could be undefined (6fd40d0)
  • node: config should use merge, findOneAndUpdate should return new (8ecd8d6)
  • node: fix some logging (da5ede5)
  • node: fixing the repair script so we can repair while a node is syncing (b1b1e17)
  • node: race condition rejects (d47ffb3)
  • node: remove wallet from websockets (b1a2d63)
  • node: removing confirmations (51ccf3f)
  • node: removing limits on wallet address endpoint (8b1515b)
  • typo - s/Payment/PaymentACK/ (7b408c3)
  • wrong output value calculation in _buildTx (2e1cc88)
  • node: removing unneeded properties (7f2ad9f)
  • node: resync uses connect (74df9b8)
  • node: stream has a memory leak, use event emitter instead (d256e5c)
  • server: Fix unconfirmed utxo results (72bf2bb)
  • sync: handle sync node going awol (372b273)

Features

  • api: Adds check wallet endpoint (a606095)
  • api: break balance response into confirmed and unconfirmed components (894cec5)

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by nitsujlangston, a new releaser for bitcore-lib since your current version.


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.


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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [lodash](https://github.com/lodash/lodash) to 4.17.21 and updates ancestor dependency [bitcore-lib](https://github.com/bitpay/bitcore). These dependencies need to be updated together.


Updates `lodash` from 3.10.1 to 4.17.21
- [Release notes](https://github.com/lodash/lodash/releases)
- [Commits](lodash/lodash@3.10.1...4.17.21)

Updates `bitcore-lib` from 0.13.19 to 10.0.5
- [Release notes](https://github.com/bitpay/bitcore/releases)
- [Changelog](https://github.com/bitpay/bitcore/blob/master/CHANGELOG.md)
- [Commits](https://github.com/bitpay/bitcore/commits/v10.0.5)

---
updated-dependencies:
- dependency-name: lodash
  dependency-type: indirect
- dependency-name: bitcore-lib
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Apr 25, 2023
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.

0 participants