Skip to content

chore(deps): bump brace-expansion from 5.0.6 to 5.0.7 - #45

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/brace-expansion-5.0.7
Open

chore(deps): bump brace-expansion from 5.0.6 to 5.0.7#45
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/brace-expansion-5.0.7

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 21, 2026

Copy link
Copy Markdown
Contributor

Bumps brace-expansion from 5.0.6 to 5.0.7.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Summary by cubic

Update brace-expansion from 5.0.6 to 5.0.7 to pull in upstream maintenance fixes and keep dependencies current. Lockfile-only change; no runtime impact expected.

Written for commit 3645bea. Summary will update on new commits.

Review in cubic

Bumps [brace-expansion](https://github.com/juliangruber/brace-expansion) from 5.0.6 to 5.0.7.
- [Release notes](https://github.com/juliangruber/brace-expansion/releases)
- [Commits](juliangruber/brace-expansion@v5.0.6...v5.0.7)

---
updated-dependencies:
- dependency-name: brace-expansion
  dependency-version: 5.0.7
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Jul 21, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@changeset-bot

changeset-bot Bot commented Jul 21, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 3645bea

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.

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

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Risk: low. Approved this patch-level brace-expansion lockfile bump; Cursor Bugbot was not present on the PR. No reviewers assigned.

Open in Web View Automation 

Sent by Cursor Approval Agent: Pull Request Router and Approver

@yakimoto

Copy link
Copy Markdown
Contributor

Superseded by #53 — please close this rather than merging it. This PR clears nothing, and I measured that rather than inferring it.

brace-expansion has two live advisories. The alert that opened this PR is the older >= 3.0.0, < 5.0.7 (fix 5.0.7). A newer one — GHSA-mh99-v99m-4gvg, range <= 5.0.7, patched in 5.0.8 — landed after it, and 5.0.7 sits inside that range.

Pinning each version in the lockfile and running npm audit with dev scope included:

brace-expansion total high still flagged?
5.0.6 (main) 3 2 yes
5.0.7 (this PR) 3 2 yes
5.0.8 (#53) 2 1 no

Merging this would close the alert cosmetically while leaving the vulnerability in the tree — the worst of both outcomes, because it also removes the signal that would prompt a real fix.

#53 goes to 5.0.8 and is verified by driving minimatch directly, not by reading the audit summary. Safe here because this repo is minimatch@10.2.5; it would not be safe on a minimatch@3 tree, which is the trap documented in wave-av/claude-workstation#554 and mapped across the fleet in wave-av/claude-workstation#562.

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.

1 participant