build(deps-dev): bump lodash from 4.17.21 to 4.17.23

[dependabot]

Bumps lodash from 4.17.21 to 4.17.23.

Commits

• dec55b7 Bump main to v4.17.23 (#6088)
• 19c9251 fix: setCacheHas JSDoc return type should be boolean (#6071)
• b5e6729 jsdoc: Add -0 and BigInt zeros to _.compact falsey values list (#6062)
• edadd45 Prevent prototype pollution on baseUnset function
• 4879a7a doc: fix autoLink function, conversion of source links (#6056)
• 9648f69 chore: remove yarn.lock file (#6053)
• dfa407d ci: remove legacy configuration files (#6052)
• 156e196 feat: add renovate setup (#6039)
• 933e106 ci: add pipeline for Bun (#6023)
• 072a807 docs: update links related to Open JS Foundation (#5968)
• 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 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 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.

---

Important

Bump lodash from 4.17.21 to 4.17.23 in package.json for security patches and improvements.

• Dependencies:
  • Bump lodash from 4.17.21 to 4.17.23 in package.json.
• Misc:
  • Update includes security patches and minor improvements.

^{This description was created by for c16e720. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to c16e720 in 1 minute and 18 seconds. Click for details.

• Reviewed 13 lines of code in 1 files
• Skipped 1 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. package.json:116

• Draft comment:
  Bump lodash in devDependencies to ^4.17.23. Note that the commit message mentions upgrading from 4.17.21, but the diff updates from ^4.17.19. Please confirm that this is intentional.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50% This comment is asking the PR author to "confirm that this is intentional" - which is explicitly against the rules. The rules state "Do NOT ask the PR author to confirm their intention, to explain, to double-check things, to ensure the behavior is intended." Additionally, the comment is about a dependency change, and the rules say "Do NOT comment on dependency changes, library versions that you don't recognize, or anything else related to dependencies." The discrepancy between the commit message and the actual diff is not something that requires action - it's just a minor inconsistency that doesn't affect the code. This is a purely informative comment that doesn't suggest a clear code change. Could there be a legitimate concern here about the version mismatch indicating a mistake in the PR? Perhaps the author intended to upgrade from a different version and this could indicate they're working from the wrong base? Even if there's a version mismatch with the commit message, this is a dependency change which the rules explicitly say not to comment on. Additionally, asking to "confirm" something is explicitly prohibited. The actual change (bumping lodash) is straightforward and correct regardless of what the commit message says. This comment should be deleted because it violates multiple rules: it asks the PR author to confirm their intention, it's about a dependency change, and it doesn't suggest a clear code change. The comment is purely informative about a minor discrepancy between the commit message and the diff.

Workflow ID: wflow_soHka3RFp1lD0nJp

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[greptile-apps]

Greptile Summary

This PR bumps lodash from 4.17.21 to 4.17.23, bringing important security and documentation improvements. The update includes a critical security fix that prevents prototype pollution in the baseUnset function (commit edadd45), along with JSDoc improvements and infrastructure updates.

• Security: Fixes prototype pollution vulnerability in baseUnset function
• Documentation: Improved JSDoc types and documentation
• Scope: lodash is listed as a dev dependency and is extensively used throughout the codebase (38+ source files)
• Impact: Low risk - version bump includes backward-compatible changes only

This is a straightforward dependency update that should be merged to address the security vulnerability.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk - it's a straightforward dependency update
• Score reflects that this is an automated dependency bump with security fixes, no code changes, and only minor version updates (4.17.21 → 4.17.23) that maintain backward compatibility
• No files require special attention

Important Files Changed

Filename	Overview
package.json	Updated lodash dev dependency from ^4.17.19 to ^4.17.23, includes security fix for prototype pollution
package-lock.json	Lockfile updated with lodash 4.17.23 resolved version and integrity hash

Sequence Diagram

sequenceDiagram
    participant Dev as Developer/Dependabot
    participant PR as Pull Request #739
    participant PJ as package.json
    participant PL as package-lock.json
    participant NPM as npm registry
    
    Dev->>PR: Create PR to update lodash
    PR->>PJ: Update lodash version ^4.17.19 → ^4.17.23
    PR->>PL: Update resolved version 4.17.21 → 4.17.23
    PR->>PL: Update integrity hash
    
    Note over PJ,PL: Changes include security fix<br/>for prototype pollution
    
    PL->>NPM: Reference lodash@4.17.23
    NPM-->>PL: Verify integrity hash
    
    Note over PR: Ready to merge<br/>Backward compatible<br/>Security improvement

Loading