Update bitwarden extension

[0xdhrv]

Description

Security: Stops the master password from appearing in error logs when users use “Copy Last Errors” or share bug reports.

• Cause: Unlock/login failures were stored as raw exec errors. Execa’s error message includes the full CLI command (bw unlock <password> --raw), so the password was included in copied logs.
• Change: Unlock and login errors are now sanitized with treatError() before being passed to captureException(), so only a redacted string is stored. Passwords are replaced with [REDACTED], and special characters in the password are escaped so redaction is reliable.
• Other: Resolved npm install peer dependency (react-devtools) and updated shortcut types (windows → Windows) for current @raycast/api.

Screencast

N/A — security/logging fix only; no UI or flow changes.

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Thank you for your contribution! 🎉

🔔 @jomifepe @daniel-stoneuk @andreaselia @pernielsentikaer @eth-p @YamenSharaf @undefinedzack @anirudhganwal06 @ivaarsson @gasparhabif @marinsokol @jose-elias-alvarez @krambono @clins1994 you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

📋 Quick checkout commands

BRANCH="ext/bitwarden"
FORK_URL="https://github.com/0xdhrv/raycast-extensions.git"
EXTENSION_NAME="bitwarden"
REPO_NAME="raycast-extensions"

git clone -n --depth=1 --filter=tree:0 -b $BRANCH $FORK_URL
cd $REPO_NAME
git sparse-checkout set --no-cone "extensions/$EXTENSION_NAME"
git checkout
cd "extensions/$EXTENSION_NAME"
npm install && npm run dev

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 10-15 business days.