Skip to content

build(deps): bump lodash from 4.17.21 to 4.17.23#83

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/lodash-4.17.23
Open

build(deps): bump lodash from 4.17.21 to 4.17.23#83
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/lodash-4.17.23

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Mar 24, 2026

Bumps lodash from 4.17.21 to 4.17.23.

Commits

Dependabot compatibility score

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.

Note

Low Risk
Low risk dependency-only change updating lodash patch version; no application code changes.

Overview
Updates the lodash dependency from 4.17.21 to 4.17.23 in package.json and package-lock.json.

The lockfile also loosens the resolved version for semantic-release-rubygem to *, affecting how that package is pinned during installs.

Written by Cursor Bugbot for commit 3a6fa02. This will update automatically on new commits. Configure here.

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

---
updated-dependencies:
- dependency-name: lodash
  dependency-version: 4.17.23
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Mar 24, 2026
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

"lodash": "4.17.23",
"semantic-release": "17.4.7",
"semantic-release-rubygem": "latest"
"semantic-release-rubygem": "*"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lockfile specifier mismatch with package.json for semantic-release-rubygem

Low Severity

The lockfile regeneration changed semantic-release-rubygem specifier from "latest" to "*" in the root packages[""] section, while package.json still declares "latest". This unintended collateral change from the lodash bump creates a mismatch that could cause npm ci to fail with an "out of sync" error depending on the npm version used in CI, since npm ci performs strict validation between package.json and package-lock.json.

Additional Locations (1)
Fix in Cursor Fix in Web

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 javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants