Update dependency fast-glob to v3.2.7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
fast-glob	3.2.2 -> 3.2.7

---

Release Notes

mrmlnc/fast-glob

v3.2.7

Compare Source

🐛 Bug fixes

The previous release (3.2.6) introduced a regression, thanks to which negative patterns were not applied to patterns outside the current directory.

This release fixes the issue.

v3.2.6

Compare Source

🐛 Bug fixes

• Now you can use patterns related to the parent directory along with the regular ones. (#​310, #​316)

// Patterns inside current directory → ['*', './*.js']
// Patterns outside current directory → ['../*', './../*.js']

// Previously you could specify a patterns outside current directory.
fg.sync(['../*.txt']) → ['../file.txt']

// But when the pattern inside current directory was added to them, the behavior broke down.
fg.sync(['*.md', '../*.txt']) → ['file.md'] // The '../file.txt' file exists

// After this fix you can mix both kinds of patterns.
fg.sync(['*.md', '../*.txt']) → ['file.md', '../file.txt']

// Right now we do not support patterns like '{.,..}/*.md'.

📖 Documentation

• Added clarifications for the followSymbolicLinks option.

⚙️ Infrastructure

• The glob-parent package has been updated to fix vulnerabilities. (#​304)
• The micromatch package has been updated to eliminate dependency on the picomatch package from this package. (#​256)
• Node.js 16 has been added to the CI configuration to run tests and benchmarks. Now benchmarks will run only on this version. (#​311)
• The tiny-glob package has been added to the synchronous product benchmarks. (#​323)
• The fdir package has been added to synchronous and asynchronous product benchmarks. The latest launch. (#​322)
• The .npmignore file has been replaced by the files field in the package.json file. (#​321)

v3.2.5

Compare Source

🐛 Bug fixes

• Now this packages correctly supports ARM processors (#​296, thanks @​yozman).
• Fixed behavior that led to Uncaught Error when the package tried to destroy stream multiple times (#​282).
  • https://github.com/nodelib/nodelib/pull/53, https://github.com/nodelib/nodelib/pull/58
• Fixed an issue with patterns that starts with the leading slash (#​277).
  • Related to patterns with various kinds: /*, /tmp/*, //?/C:/*.
  • https://github.com/nodelib/nodelib/pull/54, https://github.com/nodelib/nodelib/pull/63

📖 Documentation

• Fix examples for the markDirectories option (#​287, thanks @​yarastqt).

⚙️ Infrastructure

• Use the latest versions of OS in CI (#​279).
• Move from Azure Pipelines to GitHub Actions (#​299).

v3.2.4

Compare Source

🐛 Bug fixes

• Fixed a regression in 3.2.3 when the caseSensitiveMatch option is disabled (#​276)

v3.2.3

Compare Source

🐛 Bug fixes

• Fixed an issue when the unique option led to incorrect results when mixing static and dynamic patterns (#​268)
• Fixed an issue when the pattern starting with a forward slash (#​266)

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/logan-anderson/blog-nextjs-tina-tailwind/DCUB2vCkuZF8oc9y3qFsLzC4kEEX
✅ Preview: https://blog-nextjs-tina-tailwind-git-renovate-fa-98175f-logan-anderson.vercel.app

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (3.2.7). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.