Repository navigation
chore(deps): fix lockfile for #70 dependency bump (napi-rs/keyring 2.0.0, vitest 5.0.0) - #72
Closed
stephendolan wants to merge 2 commits into
Closed
stephendolan wants to merge 2 commits into
stephendolan wants to merge 2 commits into
Conversation
Bumps the all-dependencies group with 2 updates: [@napi-rs/keyring](https://github.com/Brooooooklyn/keyring-node) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `@napi-rs/keyring` from 1.3.0 to 2.0.0 - [Release notes](https://github.com/Brooooooklyn/keyring-node/releases) - [Commits](Brooooooklyn/keyring-node@v1.3.0...v2.0.0) Updates `vitest` from 4.1.11 to 5.0.0 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.0/packages/vitest) --- updated-dependencies: - dependency-name: "@napi-rs/keyring" dependency-version: 2.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: all-dependencies - dependency-name: vitest dependency-version: 5.0.0 dependency-type: direct:development update-type: version-update:semver-major dependency-group: all-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
Dependabot bumped @napi-rs/keyring to 2.0.0 and vitest to 5.0.0 in package.json but did not update bun.lock, which would break a frozen-lockfile install. This regenerates bun.lock against the bumped package.json. Verified: typecheck, build, lint, and full test suite (98 tests) all pass against the updated lockfile. Supersedes #70 (adds the missing lockfile update).
Owner
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Dependabot PR #70 bumped
@napi-rs/keyring(1.2.0 → 2.0.0, major) andvitest(4.0.4 → 5.0.0, major) inpackage.json, but did not updatebun.lock— installing with a frozen lockfile would fail or silently keep the old resolved versions.This branch regenerates
bun.lockagainst the bumpedpackage.jsonfrom #70.Verification (all green against the updated lockfile)
bun install— resolves cleanly, no peer conflictsbun run typecheck— passesbun run test— 98/98 tests passbun run build— tsup build succeedsbun run lint— oxlint clean@napi-rs/keyring'sEntryAPI (used insrc/lib/auth.tsfor credential storage) is unchanged across the major bump — no source changes needed.Merge note
This is a scheduled Dependabot triage run — not auto-merged. Please review and merge manually (or close #70 in favor of this once merged, since this includes everything from #70 plus the lockfile fix).
🤖 Generated with automated Dependabot triage