Bump lodash and elasticsearch

[dependabot]

Bumps lodash to 4.18.1 and updates ancestor dependency elasticsearch. These dependencies need to be updated together.

Updates lodash from 4.17.4 to 4.18.1

Release notes

Sourced from lodash's releases.

4.18.1

Bugs

Fixes a ReferenceError issue in lodash lodash-es lodash-amd and lodash.template when using the template and fromPairs functions from the modular builds. See lodash/lodash#6167

These defects were related to how lodash distributions are built from the main branch using https://github.com/lodash-archive/lodash-cli. When internal dependencies change inside lodash functions, equivalent updates need to be made to a mapping in the lodash-cli. (hey, it was ahead of its time once upon a time!). We know this, but we missed it in the last release. It's the kind of thing that passes in CI, but fails bc the build is not the same thing you tested.

There is no diff on main for this, but you can see the diffs for each of the npm packages on their respective branches:

• lodash: lodash/lodash@4.18.0-npm...4.18.1-npm
• lodash-es: lodash/lodash@4.18.0-es...4.18.1-es
• lodash-amd: lodash/lodash@4.18.0-amd...4.18.1-amd
• lodash.templatelodash/lodash@4.18.0-npm-packages...4.18.1-npm-packages

4.18.0

v4.18.0

Full Changelog: lodash/lodash@4.17.23...4.18.0

Security

_.unset / _.omit: Fixed prototype pollution via constructor/prototype path traversal (GHSA-f23m-r3pf-42rh, fe8d32e). Previously, array-wrapped path segments and primitive roots could bypass the existing guards, allowing deletion of properties from built-in prototypes. Now constructor and prototype are blocked unconditionally as non-terminal path keys, matching baseSet. Calls that previously returned true and deleted the property now return false and leave the target untouched.

_.template: Fixed code injection via imports keys (GHSA-r5fr-rjxr-66jc, CVE-2026-4800, 879aaa9). Fixes an incomplete patch for CVE-2021-23337. The variable option was validated against reForbiddenIdentifierChars but importsKeys was left unguarded, allowing code injection via the same Function() constructor sink. imports keys containing forbidden identifier characters now throw "Invalid imports option passed into _.template".

Docs

• Add security notice for _.template in threat model and API docs (#6099)
• Document lower > upper behavior in _.random (#6115)
• Fix quotes in _.compact jsdoc (#6090)

lodash.* modular packages

Diff

We have also regenerated and published a select number of the lodash.* modular packages.

These modular packages had fallen out of sync significantly from the minor/patch updates to lodash. Specifically, we have brought the following packages up to parity w/ the latest lodash release because they have had CVEs on them in the past:

• lodash.orderby
• lodash.tonumber
• lodash.trim
• lodash.trimend
• lodash.sortedindexby
• lodash.zipobjectdeep
• lodash.unset
• lodash.omit
• lodash.template

Commits

• cb0b9b9 release(patch): bump main to 4.18.1 (#6177)
• 75535f5 chore: prune stale advisory refs (#6170)
• 62e91bc docs: remove n_ Node.js < 6 REPL note from README (#6165)
• 59be2de release(minor): bump to 4.18.0 (#6161)
• af63457 fix: broken tests for _.template 879aaa9
• 1073a76 fix: linting issues
• 879aaa9 fix: validate imports keys in _.template
• fe8d32e fix: block prototype pollution in baseUnset via constructor/prototype traversal
• 18ba0a3 refactor(fromPairs): use baseAssignValue for consistent assignment (#6153)
• b819080 ci: add dist sync validation workflow (#6137)
• Additional commits viewable in compare view

Updates elasticsearch from 14.0.0 to 16.7.3

Changelog

Sourced from elasticsearch's changelog.

[[changelog]] == Changelog

=== Versions

==== 16.7.2 (Nov 30 2020)

• use undefined as the default ssl ciphers to address a backwards-compatibility issue in node 15.3 nodejs/node#36292

==== 16.7.1 (Mar 26 2020)

• apiVersions before 7.6 restored after feedback in elastic/elasticsearch-js-legacy#28

==== 16.7.0 (Mar 25 2020)

• apiVersion "7.6" is now the default
• "7.6" is now the only apiVersion in the version 7 major version

==== 16.6.0 (Jan 15 2020)

• apiVersion "7.5" is now the default

==== 16.5.0 (Oct 31 2019)

• apiVersion "7.4" is now the default

==== 16.4.0 (Jul 10 2019)

• apiVersion "7.3" is now the default

==== 16.3.0 (Jul 10 2019)

• Removed many development dependencies
• Switched to standard + prettier linting config. Testing indicates that this doesn't have any effect on the external API but it produces thousands of changes so releasing as a minor version bump just to be safe.

==== 16.2.0 (Jul 3 2019)

• apiVersion "7.2" is now the default
• Dropped support for old 6.7 version

==== 16.1.1 (Jun 4 2019)

• Updated readme

==== 16.1.0 (May 29 2019)

• apiVersion "7.1" is now the default

==== 16.0.0 (May 2 2019)

• apiVersion "7.0" is now the default
• Dropped support for old 6.x versions, and all versions before 5.6

==== 15.5.0 (May 1 2019)

• apiVersion "6.7" is now the default

==== 15.4.1 (Feb 6 2019)

• Drop support for old versions in the 5.x line, only 5.6 is maintained

==== 15.4.0 (Feb 6 2019)

• apiVersion "6.6" is now the default

... (truncated)

Commits

• See full diff in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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.