build(deps): bump smol-toml from 1.6.1 to 1.8.0 - #4398
dependabot[bot] wants to merge 2 commits into
Conversation
Bumps [smol-toml](https://github.com/squirrelchat/smol-toml) from 1.6.1 to 1.8.0. - [Release notes](https://github.com/squirrelchat/smol-toml/releases) - [Commits](squirrelchat/smol-toml@v1.6.1...v1.8.0) --- updated-dependencies: - dependency-name: smol-toml dependency-version: 1.8.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Looks good, mechanical Dependabot version bump with no code changes needed.
What was reviewed: confirmed the entire diff is a single yarn.lock update bumping smol-toml from 1.6.1 to 1.8.0 (version, resolution, and checksum fields), still satisfying the existing ^1.5.2 range; no source, config, or documentation files changed; the linked release notes show no breaking changes (perf improvements, a stringify feature for temporal objects, and an internal type-declaration fix) between 1.6.1 and 1.8.0.
Extended reasoning...
Overview
The diff touches only yarn.lock, bumping the resolved version and checksum of the smol-toml package from 1.6.1 to 1.8.0. This is an automated Dependabot dependency update PR with no accompanying source, config, or documentation changes.
Security risks
None identified. smol-toml is a TOML parser/serializer used as a dependency; the version bump is within the existing semver range (^1.5.2) already declared in package.json, so no new dependency was introduced and no manifest changes were needed. The release notes between 1.6.1 and 1.8.0 describe a stringify feature for temporal objects, parser performance refactors, and internal packaging/type-declaration fixes — nothing indicating a change in security posture. One release note even references a fixed advisory (GHSA-7w5x-hrqm-74c2) in v1.7.1, meaning this bump moves past a previously fixed security issue rather than introducing one.
Level of scrutiny
This warrants minimal scrutiny. It is a single-line, auto-generated lockfile change from a trusted automation (Dependabot) with no logic, configuration, or build changes. The bug hunting system found no issues, and the change is fully mechanical and easily reversible if problems arise.
Other factors
No CODEOWNERS restrictions apply (none found), no CLAUDE.md conventions are relevant, and there is no PR conversation history requiring follow-up. The change is self-contained and low-risk, fitting the criteria for straightforward approval.
Bumps smol-toml from 1.6.1 to 1.8.0.
Release notes
Sourced from smol-toml's releases.
Commits
6d0f477chore: bump version97e9713docs: mention temporal api7a3068dperf: ubench opt forinstanceof Date7e8c09afeat: stringify temporal19239d0chore: bump version5f55c3achore: revert sourcemap publishing5c26f1bchore: update benchmarks92832d2refactor: better logic orchestration in structs2fb9ab8refactor: ctx object instead of pointer arg + tuple returnse6017c4ci: use staged publishDependabot 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.