* Update sdk-internal to 0.2.0-main.1230
* Drop obsolete AccessBadgeState cast in cipher-view-banner spec
`AccessBadgeState` now includes "unavailable" as of sdk-internal
0.2.0-main.1224, so the version-gated `UNAVAILABLE` double cast is no
longer needed. The literal assigns directly at each call site.
---------
Co-authored-by: bw-ghapp[bot] <178206702+bw-ghapp[bot]@users.noreply.github.com>
* Update sdk-internal to 0.2.0-main.1202
* Implement PIN length storage in JsWasmStateBridge
sdk-internal 0.2.0-main.1202 adds required set/get/clear_pin_length members to WasmStateBridge (bitwarden/sdk-internal#1708). The SDK stores the PIN's character count unencrypted so a lock screen can read it while locked, so it is backed by a new PIN_DISK state key that clears on logout.
---------
Co-authored-by: bw-ghapp[bot] <178206702+bw-ghapp[bot]@users.noreply.github.com>
* [deps] Platform: Update electron to v43.8.1 [SECURITY]
* Bump electron to 43.8.3
---------
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Daniel James Smith <djsmith85@users.noreply.github.com>
* [PM-42213] refactor: Use SDK admin attachment client for admin attachment creation
sdk-internal moves the admin flag off CreateAttachmentRequest and onto
AttachmentAdminClient::create_attachment, and drops the is_admin argument
from CiphersClient.update_collection. Route admin attachment creation through
attachments().admin() and drop the redundant update_collection argument.
* bump sdk version
* Take the CLI storage file lock synchronously
Every storage access takes a cross-process lock on data.json. It was
acquired asynchronously, so concurrent accesses within one process
found the lock held by their own process and backed off 100-250 ms
each; 10 concurrent reads scheduled 45 backoffs.
The storage actions are synchronous, so take the lock with lockSync and
lock, act and release in one synchronous step. No other access of this
process can run while the lock is held, so it never waits for itself.
Only another process holding the lock still makes it wait, with the
same backoff as before.
* Remove unused @types/retry dependency
The retry import was dropped when the storage lock became
synchronous. Nothing references the types directly anymore.
* [PM-42819] Route CLI cross-instance Send receive through SendReceiveClient
Build a receive-scoped SDK client pointed at the Send link's server instead
of reintroducing a generic ephemeral client on SdkService. Gated behind
pm-30110-sdk-sends-api; same-instance receives are unchanged.
* [PM-42819] Mint cross-instance Send access tokens through SendReceiveClient
Run the whole cross-instance receive flow (token minting, password hashing,
email/OTP exchange, access, download, decrypt) through the receive-scoped SDK
client so nothing touches the signed-in instance. Pass the device identifier
and CLI user agent to the SDK client. Legacy path is unchanged when the flag
is off or the Send is on the configured server.
* [PM-42819] Use NotFound SDK variant and share send access token helpers
Detect a missing Send in the CLI receive command via the SDK's NotFound
variant instead of matching the error message. Move the SDK credential and
token-error helpers into libs/common send-access utils shared by
DefaultSendTokenService and the receive command.
* [PM-42819] Update sdk-internal to 0.2.0-main.1127
Pick up SendReceiveClient and the NotFound error variant from the merged
sdk-internal PR (bitwarden/sdk-internal#1586).
* Do not hit endpoint of prefillFromVerifiedDomains if the user cannot manage domain verification
* Utilizes new endpoint for invite by link tab of modal
* Utilize mini endpoint going forward
* Revert changes to frontend for adding new method for API call. API calls get added to SDK going forward
* Fixing up clients code to support latest changes to SDK method changes
* Fixes via PR comments from Brandon
* Fix tech debt comment from claude for PR
* Update to latest SDK
* [deps] Platform: Update jest-environment-jsdom to v30
* Fix jsdom 26 test compatibility for jest-environment-jsdom v30
jsdom 26 defines its [LegacyUnforgeable] globals (window, document,
location, top) as non-configurable, so tests that replace them with
Object.defineProperty or jest.spyOn now throw "Cannot redefine property".
Add a jsdom test environment composed via @jest/environment-jsdom-abstract
that relaxes only those four globals to configurable, and use it for all
Angular-based projects. Also drop two assertions that only observed jsdom's
internal getComputedStyle-to-element.style delegation, and refresh snapshots
for jsdom 26's quoted url("...") CSS serialization.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Andreas Coroiu <andreas.coroiu@gmail.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* Update sdk-internal to 0.2.0-main.1087
* Use AcceptInviteLinkError for open org invite accept failures
sdk-internal 3b250ef5 (bitwarden/sdk-internal#1514) split a new
AcceptInviteLinkError enum out of InviteLinkError and moved the
RecoveryKeyMismatch variant onto it. accept_and_optionally_confirm now
rejects with AcceptInviteLinkError, so classifyOpenOrgInviteAcceptError
must guard with isAcceptInviteLinkError; the old guard narrowed to a
variant union that no longer contains RecoveryKeyMismatch (TS2367).
The spec helpers fabricate errors by setting `name`, which is what the
wasm type guard matches on, so they move to "AcceptInviteLinkError" too.
Message-text matching in classifyOpenOrgInviteAcceptApiError is left
alone: the SDK still surfaces legacy-format server responses as the Api
variant, and mapping the new typed variants onto OpenOrgInviteAcceptError
kinds is not one-to-one. The existing TODO stays.
---------
Co-authored-by: bw-ghapp[bot] <178206702+bw-ghapp[bot]@users.noreply.github.com>
* Update sdk-internal to 0.2.0-main.1083
* Implement SharedUnlockDriver.on_peer_state stub
bitwarden/sdk-internal#1491 ("feat(shared-unlock): add peer state reporting
for CLI unlock") added a new required `on_peer_state` method to the
`SharedUnlockDriver` interface, breaking `JsSharedUnlockDriver` (TS2420) and
its construction site in `DefaultSharedUnlockPeerService` (TS2345).
No TypeScript consumer of peer lock state exists yet, so the method is
implemented as an empty no-op rather than a throw: the SDK invokes it on
every accepted sync and the wasm shim logs-and-swallows rejections, so a
throwing stub would produce error noise with no behavioral benefit.
---------
Co-authored-by: bw-ghapp[bot] <178206702+bw-ghapp[bot]@users.noreply.github.com>