chore(deps): sync bun.lock for @napi-rs/keyring 2.0.0 + vitest 5.0.0 (completes #49) - #50
Open
stephendolan wants to merge 2 commits into
Open
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>
Completes #49. Dependabot's PR only bumped package.json (semver ranges ^2.0.0 / ^5.0.0); bun.lock stayed pinned at @napi-rs/keyring 1.2.0 and vitest 4.0.16. CI passes either way since 'bun install' isn't run with --frozen-lockfile, but merging as-is would leave main with a lockfile that doesn't match package.json. Verified locally: bun install, bun run typecheck, bun run lint, bun test (45 pass), bun run build — all clean. 🤖 Generated as part of scheduled Dependabot triage.
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
1 participant
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.
Completes/replaces the lockfile gap in #49 (Dependabot:
@napi-rs/keyring1.3.0 -> ^2.0.0,vitest4.1.11 -> ^5.0.0).Dependabot's PR only bumped
package.json;bun.lockstayed pinned at the old versions. CI on #49 is green regardless (this repo'sbun installstep isn't run with--frozen-lockfile, so it silently re-resolves), but merging #49 as-is would leavemainwith abun.lockthat doesn't matchpackage.json.This branch is #49's commit plus a regenerated
bun.lock— nothing else changed. Both majors are non-breaking for this codebase:@napi-rs/keyring2.0.0's breaking change (errors throw instead of returning null) is already absorbed — every keyring call insrc/lib/auth.tsis wrapped in try/catch.vitest5.0.0 required no test-file changes.Verified locally:
bun install,bun run typecheck,bun run lint,bun test(45 pass),bun run build— all clean.Merge approval is via Fortress per Stephen's review — not auto-merged. Once this lands, #49 should be closed as superseded.
🤖 Generated as part of scheduled Dependabot triage.