Bump glob and eslint-config-next

[dependabot]

Bumps glob to 10.5.0 and updates ancestor dependency eslint-config-next. These dependencies need to be updated together.

Updates glob from 10.3.10 to 10.5.0

Changelog

Sourced from glob's changelog.

changeglob

12

• Remove the unsafe --shell option. The --shell option is now ONLY supported on known shells where the behavior can be implemented safely.

11.1

GHSA-5j98-mcp5-4vw2

• Add the --shell option for the command line, with a warning that this is unsafe. (It will be removed in v12.)
• Add the --cmd-arg/-g as a way to safely add positional arguments to the command provided to the CLI tool.
• Detect commands with space or quote characters on known shells, and pass positional arguments to them safely, avoiding shell:true execution.

11.0

• Drop support for node before v20

10.4

• Add includeChildMatches: false option
• Export the Ignore class

10.3

• Add --default -p flag to provide a default pattern
• exclude symbolic links to directories when follow and nodir are both set

10.2

• Add glob cli

10.1

• Return '.' instead of the empty string '' when the current working directory is returned as a match.
• Add posix: true option to return / delimited paths, even on Windows.

10.0.0

• No default exports, only named exports

... (truncated)

Commits

• 56774ef 10.5.0
• 1e4e297 bin: Do not expose filenames to shell expansion
• 1f0c1ca 10.4.5
• eaf31dc whatever, just allow any engines
• 7827516 10.4.4
• d06c8f8 restore support for node 14.latest and 16.latest
• c14b787 10.4.3
• 8a69def node 14 no longer supported
• eef7ea3 10.4.2
• c76a7d2 use package-json-from-dist to look up package.json
• Additional commits viewable in compare view

Updates eslint-config-next from 14.2.5 to 16.0.3

Release notes

Sourced from eslint-config-next's releases.

v16.0.3

Core Changes

• fix: Rspack throw error when using ForceCompleteRuntimePlugin: #85221
• fix: build CLI output not displaying Proxy (Middleware) when nodejs runtime: #85403
• fix: staleTimes.static should consistently enforce a 30s minimum: #85479
• [turbopack] fix build of empty entries of pages: #84873
• Cache the head separately from the route tree: #84724
• Allow inspecting dev server on default port with next dev --inspect: #85037
• Avoid proxying React modules through workUnitStore: #85486
• fix: redirect should always return updated router state: #85533
• Upgrade React from b4455a6e-20251027 to 4f931700-20251029: #85518
• [turbopack] Move generation of cacheLife types out of the webpack plugin and into the dev bundler directly: #85539
• Ensure user-space stack frame for 'use cache' in page/layout component: #85519
• Update parallel routes in build-complete: #85546
• fully remove clientSegmentCache flag: #85541
• [turbopack] Support relative paths in turbopack source maps.: #85146
• Release unnecessary memory on hydration finish: #84967
• Preserve interception markers in parameter types: #85526
• move segment cache entries to top level segment-cache dir: #85542
• Upgrade React from 4f931700-20251029 to 561ee24d-20251101: #85670
• [devtools] Remove title from preferences: #85698
• Update font data: #85708
• Don't invalidate hot reloader excessively during dev server boot: #85732
• [codemod] fix: next-lint-to-eslint-cli did not handle 'next' plugin: #85749
• Upgrade React from 561ee24d-20251101 to 67f7d47a-20251103: #85762
• Tracing: Fix memory leak in span map: #85529
• Fix documentation typo in refresh function: #85696
• fix: eslint-config-next types was exporting to dist/src: #85768
• Upgrade React from 67f7d47a-20251103 to f646e8ff-20251104: #85772
• remove unused RSC payload property: #85746
• [runtime prefetching]: fix runtime prefetching when deployed: #85595
• Turbopack: next build --analyze: #85197
• Build: Log amount of workers during static generation: #85706
• Upgrade React from f646e8ff-20251104 to dd048c3b-20251105: #85819
• Sync devFallbackParams when generateStaticParams change: #85741
• chore: upgrade rspack 1.6.0: #84210
• [mcp] get_routes mcp tool: #85773
• Split each path param into a separate cache key : #85758
• [turbopack] change server source maps in production to use relative paths: #85576
• fix: skip collecting metadata for app-error in webpack: #85892
• fix: support root span attributes with a custom server: #85521
• fix isDynamicRSC condition when deployed: #85919
• [turbopack] Make it possible to synchronously access native bindings: #85787
• Upgrade React from dd048c3b-20251105 to fa50caf5-20251107: #85906
• Fix telemetry event loss on build failures and server shutdown: #85867
• Remove one stack frame from 'use cache' call stacks: #85966
• Upgrade React from fa50caf5-20251107 to 52684925-20251110: #85980
• Deployment adapter: fix metadata for "/" route: #85820
• Enable React's default Transition indicator behind a flag: #86000

... (truncated)

Commits

• 2eda33c v16.0.3
• b76f1db fix: eslint-config-next types was exporting to dist/src (#85768)
• 01014d4 v16.0.2
• e08402b v16.0.1
• 163fc17 v16.0.1-canary.6
• c72b426 v16.0.1-canary.5
• 213c425 v16.0.1-canary.4
• 234984c v16.0.1-canary.3
• 498349c v16.0.1-canary.2
• a8e1557 v16.0.1-canary.1
• 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.

[github-management-service]

It looks like you are reviewing a Dependabot upgrade PR! 🛠️
That’s great! Keeping our packages up to date to fix security issues in our stack is super important. Team Application Security wants to help make this process as easy and low friction as possible while still moving at pace.

We aim to merge Dependabot PRs within the below timeframes. The objectives are based on the severity of the security vulnerability we are mitigating with the upgrade:

Severity	Target Merge (days)
CRITICAL	7 days
HIGH	14 days
MEDIUM	30 days
LOW	90 days

🎯 Target merge date for this PR: 03/12/2025 🎯

FAQ

What if we aren’t vulnerable to this particular CVE? Do we still have to upgrade the package?

It’s still a good idea to upgrade the package if we can. With new code patterns and paths being introduced every day, we have no guarantee that we won’t later make ourselves vulnerable. Keeping packages up to date as a matter of due course is also good hygiene.

What if we’re not vulnerable and upgrading is going to be a lot of work?

In these cases it’s a good idea to list out the steps you took to confirm we are not vulnerable in this PR. The PR can then be closed and the corresponding Dependabot Alert should be dismissed with the triage steps included as a comment. Please get in touch with Team Application Security via #ask-security before dismissing any CRITICAL alerts.

This is a major version upgrade that requires substantial code refactoring. What should I do?

If the upgrade requires substantial refactoring then it is possible that we will miss the objectives we have outlined above. In these cases, you should add the dependabot-refactor-required label to this PR and ping #ask-security for further advice.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	eslint-config-next@​14.2.5 ⏵ 16.0.3	+1		+3	+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		License policy violation: npm caniuse-lite under CC-BY-4.0 License: CC-BY-4.0 (npm metadata) License: CC-BY-4.0 (package/LICENSE) License: CC-BY-4.0 (package/package.json) From: package-lock.json → npm/next@14.2.32 → npm/eslint-config-next@16.0.3 → npm/caniuse-lite@1.0.30001756 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001756. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report