Skip to content

Update enhanced-resolve 5.19.0 → 5.20.1 (minor)#19845

Open
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/pnpm/enhanced-resolve-5.20.1
Open

Update enhanced-resolve 5.19.0 → 5.20.1 (minor)#19845
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/pnpm/enhanced-resolve-5.20.1

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Mar 23, 2026

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

What changed?

✳️ enhanced-resolve (5.19.0 → 5.20.1) · Repo

Release Notes

5.20.1

Patch Changes

5.20.0

Features

  • Added the baseUrl option to override the tsconfig.json's baseUrl
  • Enabled trailing commas support for JSONC

Fixes

  • Detect circular extends to prevent infinite loop in tsconfig.json
  • Support JSONC comments in tsconfig.json

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

Commits

See the full diff on Github. The new version differs by 19 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 March 23, 2026 22:55
@depfu depfu bot added the depfu label Mar 23, 2026
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 23, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: a3a645cf-3579-4e0d-ba04-6e1d0f5661ea

📥 Commits

Reviewing files that changed from the base of the PR and between 2c1ef9e and 85be112.

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

Walkthrough

This change updates the enhanced-resolve dependency across four Tailwind CSS packages. The version is bumped from ^5.19.0 to ^5.20.1 in:

  • packages/@tailwindcss-cli/package.json
  • packages/@tailwindcss-node/package.json
  • packages/@tailwindcss-standalone/package.json
  • packages/@tailwindcss-upgrade/package.json

Each package.json file has one line modified. No other dependencies, scripts, exports, or package configuration details were altered.

🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: updating enhanced-resolve from version 5.19.0 to 5.20.1, with a note that it's a minor update.
Description check ✅ Passed The description is fully related to the changeset, providing detailed release notes, commit history, and context for the enhanced-resolve dependency update across multiple packages.

✏️ 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.

@depfu
Copy link
Contributor Author

depfu bot commented Mar 23, 2026

Sorry, but the merge failed with:

At least 1 approving review is required by reviewers with write access.

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

Labels

0 participants