fix(deps): update dependency @napi-rs/keyring to v2.1.0 - #2383
Conversation
🦋 Changeset detectedLatest commit: 8d65e44 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@tailor-platform/create-sdk
@tailor-platform/eslint-plugin-sdk
@tailor-platform/sdk
@tailor-platform/sdk-plugin-seed
@tailor-platform/sdk-plugin-setup
@tailor-platform/sdk-plugin-tailordb-erd
commit: |
🤖 Claude Dependency Review✅ Recommended ActionsNone — safe to merge as-is. 📦 Update Summary
📝 Release NotesWhat's Changed:
Full Changelog: Brooooooklyn/keyring-node@v2.0.0...v2.1.0 🔐 Security Assessment
🚨 Breaking ChangesNone. This is a fully backwards-compatible minor release. The new Linux credential store selection feature adds an optional third parameter to the ✨ Main ChangesNew Feature: Linux Credential Store SelectionAdds optional control over Linux credential backend selection through a new options parameter: // New optional third parameter (backwards compatible)
new Entry('service', 'account', { linux: { store: 'secret-service' } })
new Entry('service', 'account', { linux: { store: 'keyutils' } })
Entry.withTarget('target', 'svc', 'user', { linux: { store: 'keyutils' } })Behavior:
Why this matters: Previously, credentials could silently fall back from Secret Service (durable storage) to keyutils (in-memory only), which could lead to unexpected credential loss. Explicit pinning prevents this scenario when desired. Maintenance Updates
🔍 Impact Analysis📁 Usage Locations
Test Files (Mocked)The library is mocked in 11 test files to avoid keyring dependencies during testing:
Impact: ✅ No changes needed - test mocks remain compatible with the updated API since the new parameter is optional. SummaryThis update introduces an opt-in feature for Linux users who need explicit control over credential storage backends. The SDK's current usage pattern (2-parameter constructor calls) is fully compatible with v2.1.0, and no code changes are required. |
Code Metrics Report (packages/sdk)
Details | | main (5f6664a) | #2383 (9c12832) | +/- |
|--------------------|----------------|-----------------|------|
| Coverage | 84.1% | 84.1% | 0.0% |
| Files | 526 | 526 | 0 |
| Lines | 21520 | 21520 | 0 |
| Covered | 18103 | 18103 | 0 |
| Code to Test Ratio | 1:0.5 | 1:0.5 | 0.0 |
| Code | 166156 | 166156 | 0 |
| Test | 88288 | 88288 | 0 |SDK Configure Bundle Size
Runtime Performance
Type Performance (instantiations)
Reported by octocov |
This PR contains the following updates:
2.0.0→2.1.0Release Notes
Brooooooklyn/keyring-node (@napi-rs/keyring)
v2.1.0Compare Source
What's Changed
Full Changelog: Brooooooklyn/keyring-node@v2.0.0...v2.1.0
Configuration
📅 Schedule: (in timezone Asia/Tokyo)
* 9-18 * * 1-5)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.