Skip to content

Update dependency brace-expansion@>=2.0.0 <2.1.7 to v5 - #763

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/brace-expansion-=2.0.0-2.1.7-5.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/brace-expansion-=2.0.0-2.1.7-5.x

Conversation

@renovate

@renovate renovate Bot commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
brace-expansion@>=2.0.0 <2.1.7 [^2.1.7 → ^5.0.0](https://renovatebot.com/diffs/npm/brace-expansion@>=2.0.0 <2.1.7/2.1.7/5.0.12) age confidence

Release Notes

juliangruber/brace-expansion (brace-expansion@>=2.0.0 <2.1.7)

v5.0.12

Compare Source

v5.0.11

Compare Source

v5.0.10

Compare Source

v5.0.9

Compare Source

v5.0.8

Compare Source

v5.0.7

Compare Source

v5.0.6

Compare Source

v5.0.5

Compare Source

v5.0.4

Compare Source

v5.0.3

Compare Source

v5.0.2

Compare Source

v4.0.1

Compare Source


v4.0.0

Compare Source

As a precaution to not risk breaking anything with 278132b, this is a new semver major release

v3.0.9

Compare Source

v3.0.8

Compare Source

v3.0.7

Compare Source

v3.0.6

Compare Source

v3.0.5

Compare Source

v3.0.4

Compare Source

v3.0.3

Compare Source

v3.0.2

Compare Source

v3.0.1

Compare Source


v3.0.0

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • 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 was generated by Mend Renovate. View the repository job log.

@changeset-bot

changeset-bot Bot commented Oct 22, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 8a9d217

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Devin Review found 1 potential issue.

Devin Review

Comment thread pnpm-lock.yaml
minimatch@9.0.9:
dependencies:
brace-expansion: 2.1.7
brace-expansion: 5.0.12

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟡 Glob tools fail on supported Node releases

On Node 20.0–20.18 or 22.0–22.11, minimatch@9.0.9 cannot require the ESM-only brace-expansion v5. Glob and import-sort tooling fail with ERR_REQUIRE_ESM.

Learn more

The lockfile installs brace-expansion v5 as the dependency of minimatch@9. Minimatch 9's CommonJS entry point loads brace-expansion with require(), while brace-expansion v5 is an ES module. Older Node 20 and 22 releases cannot load it through require(). Both glob and the import-sort plugin depend on minimatch 9, so their CommonJS usage fails before matching begins.

Example: On Node 20.18, a tool imports glob@10.5.0; glob loads minimatch, whose CommonJS entry requires brace-expansion v5 and raises ERR_REQUIRE_ESM.

Recommended fix: Keep minimatch 9 on patched brace-expansion 2.1.7, or upgrade its consumers to minimatch versions that load brace-expansion v5 correctly. Test on the earliest Node 20 and 22 versions the project supports.

Devin Review


Was this helpful? React with 👍 or 👎 to provide feedback.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants