Bump path-to-regexp from 0.1.12 to 0.1.13 in /preview#1448
Conversation
Bumps [path-to-regexp](https://github.com/pillarjs/path-to-regexp) from 0.1.12 to 0.1.13. - [Release notes](https://github.com/pillarjs/path-to-regexp/releases) - [Changelog](https://github.com/pillarjs/path-to-regexp/blob/v.0.1.13/History.md) - [Commits](pillarjs/path-to-regexp@v0.1.12...v.0.1.13) --- updated-dependencies: - dependency-name: path-to-regexp dependency-version: 0.1.13 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
LGTM — security patch bumping path-to-regexp to fix CVE-2026-4867, only affects preview/package-lock.json.
Extended reasoning...
Overview
This is a Dependabot-generated patch bump of the path-to-regexp transitive dependency from 0.1.12 to 0.1.13, confined to preview/package-lock.json. The only change is the version string, resolved URL, and integrity hash for that one package.
Security risks
The bump explicitly addresses CVE-2026-4867 (GHSA-37ch-88jc-xwx2), a security advisory in path-to-regexp. Applying the patch reduces risk; not applying it leaves a known vulnerability in place. The change itself introduces no new security surface.
Level of scrutiny
This is a minimal, mechanical lock-file update in a preview/ subdirectory (not the main SDK production build). The diff is three lines and fully generated by Dependabot. No logic or behaviour changes are possible from a lock-file-only bump.
Other factors
No bugs were found by the automated bug-hunting system. No prior reviews or unresolved comments exist. The change is a straightforward security fix with high Dependabot compatibility confidence.
Bumps path-to-regexp from 0.1.12 to 0.1.13.
Release notes
Sourced from path-to-regexp's releases.
Changelog
Sourced from path-to-regexp's changelog.
Commits
9fd0c870.1.13 (#425)7ccf02cfix: CVE-2026-4867Maintainer changes
This version was pushed to npm by ulisesgascon, a new releaser for path-to-regexp since your current version.
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.