chore(deps): bump smol-toml from 1.6.0 to 1.6.1 in /website#21
chore(deps): bump smol-toml from 1.6.0 to 1.6.1 in /website#21dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [smol-toml](https://github.com/squirrelchat/smol-toml) from 1.6.0 to 1.6.1. - [Release notes](https://github.com/squirrelchat/smol-toml/releases) - [Commits](squirrelchat/smol-toml@v1.6.0...v1.6.1) --- updated-dependencies: - dependency-name: smol-toml dependency-version: 1.6.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
LGTM — security patch bumping smol-toml from 1.6.0 to 1.6.1.
Extended reasoning...
Overview
This PR updates a single entry in website/package-lock.json, bumping smol-toml from 1.6.0 to 1.6.1. The change is a patch-level version bump generated by Dependabot and touches no application logic.
Security risks
The update is itself a security fix (GHSA-v3rj-xjv7-4jmq): it replaces unbounded recursion in skipVoid with an iterative approach to prevent stack overflow from attacker-controlled TOML input. Merging this PR reduces risk; not merging it leaves the vulnerability open. No new security concerns are introduced.
Level of scrutiny
Minimal scrutiny is warranted. This is a mechanical lock-file update to a patch release whose only change is a targeted bug/security fix. The diff is three lines (version string, resolved URL, and integrity hash), and there are no logic changes in this repository's own code.
Other factors
No bugs were found by the automated bug hunting system. There are no outstanding reviewer comments. The change is fully mechanical and low-risk.
Bumps smol-toml from 1.6.0 to 1.6.1.
Release notes
Sourced from smol-toml's releases.
Commits
072b64fchore: version bump19a5dc7chore: upgrade dependencies and actionsf286f87fix: don't use recursion in skipVoidDependabot 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.