Skip to content
Source
Sign inSign up
TanStack/router

Bump lodash from 4.17.11 to 4.17.15 #8

Closeddependabot[bot](GitHub profile, opens in a new tab)wants to merge 1 commit intomaster fromrefs/pull/8/headopened

Bumps lodash from 4.17.11 to 4.17.15.

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 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 ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

    1. dependabot[bot](GitHub profile, opens in a new tab) added labelsdependencies

    2. View your CI Pipeline Execution ↗ for commit 68a0a792cce62c06a4261dca60ab83f0d35b66e5

      CommandStatusDurationResult
      nx affected --targets=test:eslint,test:unit,tes...❌ Failed16m 59sView ↗
      nx run-many --target=build --exclude=examples/*...✅ Succeeded1m 54sView ↗

      ☁️ Nx Cloud last updated this comment at 2026-06-13 22:41:42 UTC

    3. Important

      At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.

      Nx Cloud has identified a possible root cause for your failed CI:

      This CI failure appears to be related to the environment or external dependencies rather than your code changes.

      No code changes were suggested for this issue.

      Trigger a rerun:

      Rerun CI

      Nx Cloud View detailed reasoning on Nx Cloud ↗


      🎓 Learn more about Self-Healing CI on [nx.dev](https://nx.dev/docs/features/ci-features/self-healing-ci?utm_source=pull-request&utm_medium=comment)

Sign in to join this conversation.