build(deps-dev): bump lodash-es from 4.17.21 to 4.18.1 in /web/tests/e2e

[dependabot]

Bumps lodash-es from 4.17.21 to 4.18.1.

Release notes

Sourced from lodash-es'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

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.

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

[kw-security]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[dj4oC]

Bumps lodash-es from 4.17.21 to 4.18.1 in web/tests/e2e/package.json (devDependency, E2E test tooling only — not shipped in the product bundle).

Findings

No blocking issues — this is a beneficial bump: 4.18.0/4.18.1 fix a prototype-pollution issue in _.unset/_.omit (GHSA-f23m-r3pf-42rh) and a code-injection issue in _.template (CVE-2026-4800/GHSA-r5fr-rjxr-66jc). Since this dependency is scoped to web/tests/e2e dev tooling, it carries no production runtime exposure either way.

One lockfile-hygiene note: only package.json changed in this diff — pnpm-lock.yaml doesn't appear to have been regenerated alongside it. Worth confirming pnpm install --frozen-lockfile still succeeds for web/tests/e2e, or has the lockfile update squashed in before merge.

Deployment topology check

N/A — test-only dependency, no runtime/deployment impact.

Verdict

Commenting

🤖 Automated review by Claude Code (security · stability · performance · coverage)

---

Generated by Claude Code

[dj4oC]

CI is red and not transient (web-build-test has been failing since this PR opened, mergeable_state: blocked) — root cause confirmed in the job logs, not a flaky run:

This PR's commit only touches web/tests/e2e/package.json (changed_files: 1) — the corresponding pnpm-lock.yaml entry was not regenerated to match, so the workspace lockfile is now out of sync with the manifest (lockfile still resolves lodash-es to 4.17.21, manifest now asks for 4.18.1). web-build-test fails with ERR_PNPM_OUTDATED_LOCKFILE as a direct result — this is a pnpm monorepo, and Dependabot's lockfile regeneration for workspace-scoped npm/yarn ecosystem updates doesn't always reach pnpm-lock.yaml correctly.

Suggested fix: comment ·@·d·ependabot r·ebase to have Dependabot regenerate the PR including the lockfile. If the same lockfile-drift happens again on rebase, that likely means Dependabot's pnpm-workspace support needs a dependabot.yml adjustment (e.g. explicit versioning-strategy or a top-level lockfile path) rather than a per-PR fix.

changelog-lint is also failing on this PR — expected/likely exempt for a pure dependency bump, but flagging in case this repo's dependency-bump PRs are supposed to carry a changelog fragment.

🤖 Automated review by Claude Code (security · stability · performance · coverage)

---

Generated by Claude Code

[dj4oC]

CI investigation: the failures here aren't caused by the lodash-es 4.17.21→4.18.1 bump itself — the jobs don't get far enough to exercise it.

• web-build-test / web-tests-passed: pnpm install --frozen-lockfile rejects the install because pnpm-lock.yaml wasn't regenerated (ERR_PNPM_OUTDATED_LOCKFILE, lockfile has 4.17.21, manifest has 4.18.1 for web/tests/e2e/package.json).
• build-and-test: fails at changelog-lint — this bump is missing a changelog fragment.

Both look like Dependabot config/lockfile hygiene gaps rather than a breaking dependency change. Suggest regenerating pnpm-lock.yaml and adding the changelog entry (or configuring Dependabot to do so) before merge.

🤖 Automated review by Claude Code (security · stability · performance · coverage)

---

Generated by Claude Code

[DeepDiver1975]

Holding: CI is failing (not a rebase conflict): build-and-test, web-build-test, web-tests-passed. A rebase won't fix this — needs a human/upstream fix.