Bump defu from 6.1.4 to 6.1.6 in /crates/aptos-batch-encryption/ts-batch-encrypt#19333
Conversation
Bumps [defu](https://github.com/unjs/defu) from 6.1.4 to 6.1.6. - [Release notes](https://github.com/unjs/defu/releases) - [Changelog](https://github.com/unjs/defu/blob/main/CHANGELOG.md) - [Commits](unjs/defu@v6.1.4...v6.1.6) --- updated-dependencies: - dependency-name: defu dependency-version: 6.1.6 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 3d8a1a1. Configure here.
| vitest: | ||
| specifier: ^3.2.4 | ||
| version: 3.2.4(@types/node@22.18.1)(jiti@2.5.1)(terser@5.44.0)(tsx@4.20.6) | ||
| lockfileVersion: '6.0' |
There was a problem hiding this comment.
Lockfile version downgraded from 9.0 to 6.0
High Severity
The lockfileVersion was downgraded from '9.0' to '6.0', indicating the lockfile was regenerated with a pnpm v8 compatible format instead of the original pnpm v9 format. This causes the entire lockfile structure to change (e.g., importers → flat dependencies/devDependencies, package format changes). If the project uses pnpm v10, this lockfile will fail to parse entirely. With pnpm v9, it will trigger an automatic lockfile upgrade on install, potentially resolving different dependency versions. This also caused unrelated dependency version changes (e.g., size-limit downgraded from 8.2.6 to 8.2.4, esbuild from 0.18.20 to 0.17.19).
Reviewed by Cursor Bugbot for commit 3d8a1a1. Configure here.


Bumps defu from 6.1.4 to 6.1.6.
Release notes
Sourced from defu's releases.
Changelog
Sourced from defu's changelog.
Commits
001c290chore(release): v6.1.6407b516build: fix mixed types23e59e6chore(release): v6.1.511ba022fix: ignore inherited enumerable properties3942bfbfix: prevent prototype pollution via__proto__in defaults (#156)d3ef16dchore(deps): update actions/checkout action to v6 (#151)869a053chore(deps): update actions/setup-node action to v6 (#149)a97310cchore(deps): update codecov/codecov-action action to v6 (#154)89df6bbchore: fix typecheck9237d9cci: bump nodeYou can trigger a rebase of this PR 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.
Note
Medium Risk
Although code is unchanged, the
pnpm-lock.yamlis fully regenerated (lockfile format/version change) and pulls in numerous transitive/dev dependency resolution updates, which can affect build/test outputs for the TypeScript package.Overview
Regenerates
ts-batch-encrypt’spnpm-lock.yaml, including the intendeddefuupgrade (viaunconfig) and a broad refresh of resolved versions across the toolchain (notablyvite,rollup,rolldown,esbuild, and related transitive packages).The lockfile format itself changes (
lockfileVersionand structure), indicating it was re-created with a different pnpm lockfile schema, which may impact dependency resolution reproducibility across environments.Reviewed by Cursor Bugbot for commit 3d8a1a1. Bugbot is set up for automated code reviews on this repo. Configure here.