Skip to content

Update globby 15.0.0 → 16.1.1 (major)#19724

Open
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/pnpm/globby-16.1.1
Open

Update globby 15.0.0 → 16.1.1 (major)#19724
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/pnpm/globby-16.1.1

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Feb 25, 2026

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ globby (15.0.0 → 16.1.1) · Repo

Release Notes

16.1.1

  • Fix negation patterns with absolute filesystem paths 72e9916

v16.1.0...v16.1.1

16.1.0


v16.0.0...v16.1.0

16.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

  • Fix {gitignore: true} performance issue fcb07c3
  • Fix bundler compatibility e6c72c9
  • Fix parent directory patterns with gitignore option 11dd2df
  • Fix ignore patterns with parent directory references a58d117
  • Fix types for stats option c10f600

v15.0.0...v16.0.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 27 commits:


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot requested a review from a team as a code owner February 25, 2026 08:10
@depfu depfu bot added the depfu label Feb 25, 2026
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 25, 2026

Walkthrough

This change updates the globby dependency in the @tailwindcss-upgrade package from version ^15.0.0 to ^16.1.1. The update modifies a single line in the package.json file and represents a minor and patch version increment. No functional code changes, control-flow alterations, or public API signature modifications are present in this pull request.

🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the main change: updating the globby dependency from version 15.0.0 to 16.1.1, which is the primary and only change in this pull request.
Description check ✅ Passed The description is directly related to the changeset, providing detailed release notes, commit information, and breaking changes associated with the globby dependency upgrade from 15.0.0 to 16.1.1.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/`@tailwindcss-upgrade/package.json:
- Line 35: The globby v16 change affects the call in
packages/@tailwindcss-upgrade/src/index.ts where globby is invoked with the
option gitignore: true (around the call site passing that option); test the repo
with globby v16 to confirm whether parent .gitignore rules now exclude files you
expect to include; if the behavior is unacceptable either (A) adjust the globby
call to gitignore: false and add explicit ignore/include patterns to replicate
the previous behavior, or (B) pin globby to v15 in package.json, or (C) update
the code to compute a custom ignore list that merges only the .gitignore files
you want—run unit/integration tests and update snapshots accordingly before
merging.

ℹ️ Review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 097f982 and cef2837.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (1)
  • packages/@tailwindcss-upgrade/package.json

"dedent": "1.7.1",
"enhanced-resolve": "^5.19.0",
"globby": "^15.0.0",
"globby": "^16.1.1",
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Find the `@tailwindcss-upgrade` package directory
UPGRADE_PKG="packages/@tailwindcss-upgrade"

# 1) Find all globby imports and usages in the `@tailwindcss-upgrade` package
echo "=== Globby imports in `@tailwindcss-upgrade` ==="
rg -n --type=ts --type=js 'globby|isGitIgnored' "$UPGRADE_PKG" || echo "No matches found"

echo ""
echo "=== Globby function calls with options ==="
rg -n -B2 -A4 'globby\s*\(' "$UPGRADE_PKG" || echo "No matches found"

echo ""
echo "=== Gitignore option usage ==="
rg -n -C3 'gitignore\s*:' "$UPGRADE_PKG" || echo "No matches found"

echo ""
echo "=== Negation pattern usage ==="
rg -n -C3 '!\s*["\']|expandNegationOnlyPatterns' "$UPGRADE_PKG" || echo "No matches found"

Repository: tailwindlabs/tailwindcss

Length of output: 2013


🌐 Web query:

globby v16 breaking changes release notes

💡 Result:

globby v16.0.0 — breaking change (release date: 2025-11-15)

  • gitignore: true now respects parent .gitignore files up to the Git repo root (when a repo is detected). Previously, globby only considered .gitignore files within the glob search path, so results may now exclude additional files/directories due to inherited ignore rules. [1][2]

Release notes / changelog: [1]

Sources

  • [1] GitHub release: globby v16.0.0 notes (Breaking/Improvements/Fixes)
  • [2] globby README (gitignore option behavior description)

Test globby v16 upgrade before merging—breaking change in gitignore behavior confirmed.

Line 99 in packages/@tailwindcss-upgrade/src/index.ts uses gitignore: true, which has a breaking behavioral change in v16: parent .gitignore files up to the Git repo root are now respected, whereas v15 only considered .gitignore files within the search path. This means file discovery in @tailwindcss/upgrade will now exclude additional files/directories inherited from parent ignore rules. Verify through testing that this new behavior is acceptable (e.g., files in subdirectories with upstream .gitignore rules are no longer unexpectedly included).

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@packages/`@tailwindcss-upgrade/package.json at line 35, The globby v16 change
affects the call in packages/@tailwindcss-upgrade/src/index.ts where globby is
invoked with the option gitignore: true (around the call site passing that
option); test the repo with globby v16 to confirm whether parent .gitignore
rules now exclude files you expect to include; if the behavior is unacceptable
either (A) adjust the globby call to gitignore: false and add explicit
ignore/include patterns to replicate the previous behavior, or (B) pin globby to
v15 in package.json, or (C) update the code to compute a custom ignore list that
merges only the .gitignore files you want—run unit/integration tests and update
snapshots accordingly before merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants