Repository navigation
build(deps): bump brace-expansion from 5.0.7 to 5.0.12 - #309
Conversation
Bumps [brace-expansion](https://github.com/juliangruber/brace-expansion) from 5.0.7 to 5.0.12. - [Release notes](https://github.com/juliangruber/brace-expansion/releases) - [Commits](juliangruber/brace-expansion@v5.0.7...v5.0.12) --- updated-dependencies: - dependency-name: brace-expansion dependency-version: 5.0.12 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
LGTM, straightforward dependency bump.
What was reviewed: the yarn.lock diff, confirming it only updates the transitive dependency brace-expansion's version (5.0.7 to 5.0.12) and its resolution/checksum fields, with no other entries touched. No source, config, or documentation files are part of this change.
Extended reasoning...
The diff touches only yarn.lock, bumping the transitive dependency brace-expansion from 5.0.7 to 5.0.12 with matching checksum update — a mechanical dependabot lockfile change with no source or config modifications. This touches no security-sensitive application code paths directly (it is a dependency version bump, which is itself a common vector for supply-chain and security patches), and the change is small, self-contained, and follows the standard dependabot pattern, so no human review is needed.
|
🎉 This PR is included in version 3.1.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
1 participant
Bumps brace-expansion from 5.0.7 to 5.0.12.
Commits
f3410155.0.1233a5ef1Merge commit from fork82479275.0.11935d78fMerge commit from forkdf7682f5.0.101ade9denpm run format6735c94Merge commit from fork4e70465chore: ensure prettier formatting (#154)fd7a5e3Bump ip-address from 10.2.0 to 10.4.0 (#152)1790143Bump uuid and@tapjs/processinfo(#120)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.