build(deps): bump devalue from 5.1.1 to 5.3.2 in /docs #892
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [devalue](https://github.com/sveltejs/devalue) from 5.1.1 to 5.3.2. - [Release notes](https://github.com/sveltejs/devalue/releases) - [Changelog](https://github.com/sveltejs/devalue/blob/main/CHANGELOG.md) - [Commits](sveltejs/devalue@v5.1.1...v5.3.2) --- updated-dependencies: - dependency-name: devalue dependency-version: 5.3.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
Deploying nuxt-devtools with
|
| Latest commit: |
319c97a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b5db5ca8.nuxt-devtools.pages.dev |
| Branch Preview URL: | https://dependabot-npm-and-yarn-docs-kqyn.nuxt-devtools.pages.dev |
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
|
|
||
| [email protected].5: | ||
| resolution: {integrity: sha512-8eabxkth9gZatlwl5TBuJnCsoTADlL6ftEr7A4qgdaTsPyreilDSnUk57SO+jfKcNtxPa22U5KK6DSeAYhpBJw==} | ||
| [email protected].7: |
There was a problem hiding this comment.
The PR description claims to update devalue from 5.1.1 to 5.3.2, but the lockfile still shows [email protected] and only contains updates to the immutable package.
View Details
Analysis
Dependabot commit message incorrectly claims devalue update but only updated immutable package
What fails: Commit 319c97a claims "bump devalue from 5.1.1 to 5.3.2" but docs/pnpm-lock.yaml still contains [email protected] (lines 2000, 7167, 8845) while only immutable package was actually updated from 4.3.5 to 4.3.7
How to reproduce:
git show 319c97a7 --stat # Shows "bump devalue from 5.1.1 to 5.3.2"
git show 319c97a7 -- docs/pnpm-lock.yaml | grep devalue # Shows no devalue changes
grep -n "devalue@" docs/pnpm-lock.yaml # Shows [email protected] still presentResult: Commit message claims security fixes from devalue 5.3.2 (disallowing array method access, disallowing __proto__ properties) are applied, but devalue remains at vulnerable 5.1.1 version
Expected: Either devalue should be updated to 5.3.2 as claimed, or commit message should accurately reflect that only immutable was updated
Source: Devalue 5.3.2 security fixes
Bumps devalue from 5.1.1 to 5.3.2.
Release notes
Sourced from devalue's releases.
Changelog
Sourced from devalue's changelog.
Commits
86a6a66Version Packages (#109)0623a47Merge commit from fork02d20e8Version Packages (#108)ae904c5fix stringify not picking up negative zero if a normal zero has appeared befo...e95b87afix pkg.repository8300172fix changeset config434d8aeVersion Packages (#106)67c8334mention support for URL/URLSearchParams/Temporal in READMEfec694dfeat: support URL and URLSearchParams (#92)2896e7bAdd support for Temporal objects (#98)Maintainer changes
This version was pushed to npm by svelte-admin, a new releaser for devalue 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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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.