Bump globby from 13.2.2 to 16.2.2

[dependabot]

Bumps globby from 13.2.2 to 16.2.2.

Release notes

Sourced from globby's releases.

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

• Support negation-only patterns 1273541
• Respect custom fs implementation from options c2eb272
• Add some more options to isGitIgnored functions e794ff9
• Improve error message for invalid cwd option 7535e6d

Fixes

... (truncated)

Commits

• 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
• ff45aa5 16.1.1
• 72e9916 Fix negation patterns with absolute filesystem paths
• 70c011b 16.1.0
• Additional commits viewable in compare view

[github-actions]

We detected some changes in packages/*/package.json or packages/*/source, and there are no updates in the .changeset directory.

If the changes are user-facing and should cause a version bump, run pnpm changeset to track your changes and include them in the next release CHANGELOG.

If you are making simple updates to repo configuration, examples, or documentation, you do not need to add a changeset.

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.