bitwarden@2025.2.1: Make portable

[o-l-a-v]

BREAKING CHANGE:

• Will not use $env:APPDATA\Bitwarden for user data anymore.
• Will not attempt to copy user data from elsewhere.

---

Builds on closed PRs by @FlawlessCasual17:

• bitwarden: Changed pre_install, added architecture, and added autoupdate hash extraction #10652
• bitwarden: Update the manifest #13077

Changes from PRs above:

• Download nsis.7z given the OS architecture, cuts download size to 1/3.
• Don't use Electron portable, which extracts to a new dir at each launch.
  • The portable version for Windows always extracts itself to the temp directory, which slows down the setup and sometimes causes the app to launch twice. bitwarden/clients#12879
• Add hash extraction on autoupdate.
• Add more reliable checkver logic.
• Delete self update info, so it won't autoupdate.
  • Bitwarden Should Use Portable Version (Current Version Leads to Non-Portable Installation) #4843

What I added:

• Kept "bin": "Bitwarden.exe".
• "shortcuts":: Use --user-data-dir=\"$dir\\data\" to have Bitwarden installed by Scoop keep its data inside Scoop.
  • Like other manifests do too: https://github.com/search?q=repo%3AScoopInstaller%2FExtras%20%22--user-data-dir%22&type=code
• Persist data.
  • Keep name of persistent directory bitwarden-appdata, thanks bitwarden@2025.2.1: Make portable #15053 (comment).

• Use conventional PR title: <manifest-name[@version]|chore>: <general summary of the pull request>
• I have read the Contributing Guide

[github-actions]

All changes look good.

Wait for review from human collaborators.

bitwarden

• Description
• License
• Hashes
• Checkver
• Autoupdate
• Autoupdate Hash Extraction

[jasongodev]

I was tagged in the previously closed PR that uses portable version of the Bitwarden. Looking at this new PR, it looks okay to me.

[pratikpc]

Is it possible in Scoop to add default arguments to the bin exe generated?

I do not use Bitwarden so am just curious if without it, this would not end up being a breaking change?

[pratikpc]

Also if possible can't the persist directory name be retained?

Otherwise, this would end up as a bigger breaking change

[o-l-a-v]

The persist dir has no function as of now, so changing it is not a breaking change.

[pratikpc]

@o-l-a-v but in portable mode is that not the user data directory?

Sorry I am not a user of Bitwarden Client but I read the code here

https://github.com/bitwarden/clients/blob/fdcb6ff7a2fbefeccbaf5b5bcd4243f8fb84c09a/apps/desktop/src/main.ts#L94

With Electron, the environment variable is set for portable builds.

https://www.electron.build/nsis.html#portable

Bitwarden has a portable target

https://github.com/bitwarden/clients/blob/fdcb6ff7a2fbefeccbaf5b5bcd4243f8fb84c09a/apps/desktop/electron-builder.json#L86

[o-l-a-v]

Damn, you're probably right @pratikpc. I read these previous discussions, but got it wrong.

• Bitwarden Should Use Portable Version (Current Version Leads to Non-Portable Installation) #4843
• bitwarden: Use portable version #8241

Probably best to keep the persist directory name, I agree.

[o-l-a-v]

/verify

[github-actions]

All changes look good.

Wait for review from human collaborators.

bitwarden

• Description
• License
• Hashes
• Checkver
• Autoupdate
• Autoupdate Hash Extraction