Bump globby from 11.0.1 to 16.2.3

[dependabot]

Bumps globby from 11.0.1 to 16.2.3.

Release notes

Sourced from globby's releases.

v16.2.3

• Fix backslash-escaped .gitignore rules 5775ffb

---

sindresorhus/globby@v16.2.2...v16.2.3

v16.2.2

• Fix: Do not enumerate ignored directories with gitignore option 8bf8f54

---

sindresorhus/globby@v16.2.1...v16.2.2

v16.2.1

• Fix gitignore ignoring an entire checkout under an anchored ancestor path (#277) e7bd988

---

sindresorhus/globby@v16.2.0...v16.2.1

v16.2.0

• Add globalGitignore option 51555b2

---

sindresorhus/globby@v16.1.1...v16.2.0

v16.1.1

• Fix negation patterns with absolute filesystem paths 72e9916

---

sindresorhus/globby@v16.1.0...v16.1.1

v16.1.0

• Add expandNegationOnlyPatterns option eb78791
• Fix: Normalize leading-slash negation patterns before task generation 59e269f

---

sindresorhus/globby@v16.0.0...v16.1.0

v16.0.0

Breaking

• Respect parent .gitignore files when gitignore option is enabled b9a9a84
  • When {gitignore: true}, Globby now searches for .gitignore files up to the Git repo root (if detected). This matches Git's actual behavior where parent .gitignore patterns apply to subdirectories. Previously, only .gitignore files within the glob search path were considered. This change could break existing code that relied on the previous, more limited behavior.

Improvements

... (truncated)

Commits

• 4f95a14 16.2.3
• 5775ffb Fix backslash-escaped .gitignore rules
• 6807768 Meta tweaks
• 14f4f47 16.2.2
• 8bf8f54 Fix: Do not enumerate ignored directories with gitignore option
• 47e7f65 16.2.1
• e7bd988 Fix gitignore ignoring an entire checkout under an anchored ancestor path (...
• 60e8167 16.2.0
• 51555b2 Add globalGitignore option
• 8d946e2 Fix CI
• 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 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)

[shopify-shipitnext]

🔎 View this PR in Shipit Next.

ℹ️ Expand to learn how to deploy and handle emergencies using Shipit Next

Overview

Shipit Next will merge your code on your behalf because this repository uses Shipit Next and its merge queue.

To ship this PR, you can either:

• Comment /shipit to enqueue this PR for merging.
• Go to this PR in Shipit Next and click on the "Ship It" button in the top-right corner.

Comment Commands

• /shipit: Enqueue this PR into the merge queue where it will eventually be merged and deployed.
• /cancel: Eject this PR from the merge queue and rebuild PRs that were enqueued after this PR.
• /shipit --jump-queue: Enqueue this PR at the top of the merge queue where it will be included in the next deploy. Use this for non-emergency situations.
  - Emergency handling procedure for this command can be found here.
• /shipit --emergency: Merge this PR directly into main and deploy to all environments once all require_for_emergency CI checks pass. Please be aware that changes deployed with this command will not be automatically rolled back.
  • Emergency handling procedure for this command can be found here.

Commands exclusive to Deploy Before Merge

• /cancel --emergency: Eject this PR from the merge and rollback any deployments containing this PR.

---

Documentation

• ℹ️ You can read how the merge queue works in Vault here.
• ⚠️ Emergency handling documentation in the Vault describes how to handle emergencies, e.g. failed canaries, broken code in production, etc.

Questions or feedback?

• Non-urgent questions can be submitted in our Discourse.
• Feedback can be submitted in our frustrations Google form.
• If you have feature requests, you may add them or vote for them in our GitHub repository.