Bump lodash and mintlify in /docs

[dependabot]

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

Updates lodash from 4.17.23 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 mintlify from 4.2.500 to 4.2.527

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.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
mindsdb	🟢 Ready	View Preview	Apr 23, 2026, 7:04 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[entelligence-ai-pr-reviews]

EntelligenceAI PR Summary

Upgrades the mintlify docs framework and its dependency tree to the latest versions.

• docs/package.json: Version bump of mintlify from ^4.2.500 to ^4.2.527
• docs/package-lock.json: Cascading lockfile updates across all @mintlify/* packages (cli, common, link-rot, prebuild, previewing, validation, models, scraping)
• lodash upgraded from 4.17.21 to 4.18.1 globally
• typescript upgraded from 5.9.3 to 6.0.3
• @stoplight/spectral-core upgraded from 1.21.0 to 1.22.0
• minimatch bumped from 3.1.2 to 3.1.5
• simple-eval replaced with expr-eval-fork in @stoplight/spectral-core
• libc constraint fields removed from optional platform-specific native binary package entries

---

Confidence Score: 3/5 - Review Recommended

Likely safe but review recommended — this PR bumps mintlify from 4.2.500 to 4.2.527 in docs/package.json along with cascading lockfile changes, which is a routine docs-tooling update with limited blast radius. However, the upgrade also pulls in typescript from 5.9.3 to 6.0.3 and lodash from 4.17.21 to 4.18.1, which are non-trivial semver jumps that warrant at least a smoke-test of the docs build pipeline and a check for any TypeScript 6.x breaking changes that could affect generated output. No automated review comments flagged specific issues, but the TypeScript major version bump in particular deserves manual verification that the docs build still compiles cleanly.

Key Findings:

• typescript jumping from 5.9.3 to 6.0.3 is a major version increment; TypeScript major releases historically introduce breaking changes to type-checking behavior, strict mode defaults, or module resolution that could silently break the docs build or any type-checked tooling in the docs/ workspace.
• lodash moving from 4.17.21 to 4.18.1 is a minor patch bump and unlikely to cause issues, but 4.18.x is an unusual release that should be verified against the lodash changelog to confirm it is not a yanked or pre-release artifact.
• The docs/package-lock.json cascading updates across @mintlify/cli, @mintlify/previewing, @mintlify/validation, @mintlify/scraping, and related packages were not individually reviewed, meaning transitive dependency changes (e.g., in @stoplight/spectral-core from 1.21.0 to 1.22.0) have not been audited for behavioral differences.
• No logic, application, or security-critical code is modified — all changes are confined to the docs/ subdirectory, limiting the risk surface to documentation build correctness rather than production runtime behavior.

Files requiring special attention

• docs/package.json
• docs/package-lock.json