Bump brace-expansion from 1.1.11 to 1.1.16 - #42
Conversation
Bumps [brace-expansion](https://github.com/juliangruber/brace-expansion) from 1.1.11 to 1.1.16. - [Release notes](https://github.com/juliangruber/brace-expansion/releases) - [Commits](juliangruber/brace-expansion@1.1.11...v1.1.16) --- updated-dependencies: - dependency-name: brace-expansion dependency-version: 1.1.16 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![lifeomic-review-bot[bot]](https://avatars.githubusercontent.com/u/29172293?s=60&v=4){kind=small}
There was a problem hiding this comment.
Upstream: unknown (author to confirm)
Scope
This PR updates only yarn.lock, pinning transitive brace-expansion from 1.1.11 to 1.1.16. That is a worthwhile security hygiene merge: upstream release notes cite ReDoS fixes and a CVE backport (CVE-2026-13149), reducing risk in the dev/test dependency tree without touching application source.
CI
CI is still pending; branch protection will gate merge once checks complete.
Regression risk
Patch-level semver within the 1.x line with no manifest edits—behavioral risk is low and limited to transitive dev tooling (e.g. minimatch consumers).
Residual risks / follow-ups
None — because the change is lockfile-only, package.json is unchanged, securitySensitivePaths is empty, and the bump addresses known security advisories with no application-code surface area.
Note: Review generated using Cursor model
composer-2.5.
This review was generated by review-bot.
Bumps brace-expansion from 1.1.11 to 1.1.16.
Release notes
Sourced from brace-expansion's releases.
Commits
447763a1.1.16d74e630fix: v1 backport for CVE-2026-13149 (#122)2203f4f1.1.150b09384Backport v5.0.6 change to v1 (#111)10c05fc1.1.141afa1b2Add opt-in { max } mitigation to v1 legacy line (#103)2fbb6a2Revert "Backport fix for GHSA-7h2j-956f-4vf2 to v1 (#101)" (#102)0d7652eBackport fix for GHSA-7h2j-956f-4vf2 to v1 (#101)6c353ca1.1.137fd684fBackport fix for GHSA-f886-m6hf-6m8v (#95)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.