Commercial CLI zips were unprefixed (bw-linux-*, bw-macos-*, bw-windows-*)
while OSS zips use bw-oss-*. Set the commercial artifact_prefix to -bit so
both license types follow bw-{license}-{os}[-arm64]-{version}.zip, and point
the snap job and snapcraft.yaml at bw-bit-linux-*.
* [PAM-121] Move shared PAM code to bit-pam and bit-pam-components
Creates two licensed libs owned by team-pam-dev and moves the shared PAM
code into them from bit-web so other clients can consume it:
- bitwarden_license/bit-pam (@bitwarden/bit-pam): framework-free
abstractions, helpers, date formatting and SDK services, usable from the
browser background. ESLint keeps Angular and the UI libraries out of it.
- bitwarden_license/bit-pam-components (@bitwarden/bit-pam-components): the
shared components, pipes, confirm dialogs and Angular-injected services.
Each lib exposes a single barrel. Split out of #22430 to reduce its size;
no behavioural changes.
* [PAM-121] Run Chromatic on bit-pam-components changes
* [PAM-121] Run prettier
* [PM-45197] refactor: Move provider domain into libs/common/src/provider
* [PM-45197] refactor: Add barrel export for libs/common/src/provider Add libs/common/src/provider/index.ts and import provider types from
@bitwarden/common/provider outside libs/common, so the folder can move
again without touching every consumer. The service implementations stay
out of the barrel because the abstraction and the implementation are
both named ProviderService. Code inside libs/common keeps relative
imports to avoid circular imports. No behavior change.
The SDK package can be built from a fork pull request. npm link runs the
package's lifecycle scripts and links its bin entries, and the job also had
an OIDC token and the GitHub App key. Download the package in a separate
job, type-check it in a job without secrets or id-token, and link it with
--ignore-scripts --no-bin-links.
The seven validate-* jobs download artifacts from the current run, which
is actions/download-artifact's default, so they never needed the custom
action's run lookup.
* [PM-44526] docs: Add SDK sync comments to vault domain and view models
Points engineers to the mirrored sdk-internal structs so model changes are also made in the SDK.
* [PM-44526] docs: Add vault CONTRIBUTING guide and SDK-first note on CipherService
Documents that new cipher operations must go through CipherSdkService, and wires the guide into Claude via CLAUDE.md.
* Revert "[PM-44526] docs: Add SDK sync comments to vault domain and view models"
This reverts commit 3d9239222e.
* [PM-44526] docs: Add path-scoped Claude rule for vault SDK sync
Replaces per-model comments with a rule that flags model drift from sdk-internal and CipherService methods that bypass CipherSdkService.
* [PM-44526] docs: Address review feedback on vault SDK sync rule
Widen rule to all data models, note SDK blob schema, point encrypt/decrypt at CipherEncryptionService, and fix password history paths.
* Whitelist vault CONTRIBUTING.md in capital letters check
chromatic-target.yml (pull_request_target, secrets inherited) ran Chromatic
for a fork PR whenever someone with write access opened, pushed to, or
clicked "Update branch" on it, so the fork's code ran with the Chromatic
project tokens without a deliberate review.
- Run chromatic-target.yml only when the shared ci:signed-build label is
added (same pattern as #23797). check-run still requires the labeler to
have write access.
- Remove the label once the build starts, so every new commit needs a
fresh review and label.
- Update the header comments in chromatic-target.yml and chromatic.yml to
describe the label instead of the manual re-run.
The allow-unsafe-pr-checkout flag in chromatic.yml stays while Chromatic
results are wanted on community PRs.
The Windows build runs in OSS and commercial matrix legs (PM-25909).
Each leg's Chocolatey step hashes its own installer, but the
install-script URL was always the non-prefixed (OSS) installer.
The commercial nupkg therefore embedded the commercial installer's
checksum with the OSS installer's URL. Once publishing switched to
the commercial nupkg (BRE-2353), Chocolatey verification for
2026.10.0 failed on a checksum mismatch.
Now each leg's URL uses its own artifact prefix, matching the
release asset commercial-Bitwarden-Installer-<version>.exe. OSS
output is byte-identical to before. The prefix is passed via env,
not inline ${{ }}, per workflow-injection convention.
Branch protection on main requires a check named `Lint`, which was the
TypeScript lint job alone. The Rust lint matrix only fed the unrequired
`Rust lint` fan-in, so Rust lint failures never blocked merging.
- Rename the TypeScript job to `Lint TypeScript`.
- Replace `rust-lint` with a `lint-gate` fan-in named `Lint` that needs
both the TypeScript job and the Rust matrix. It takes over the
required check name, so no ruleset change is needed.
- Rename the locales-lint job to `Lint locales` so it no longer reports
a second check named `Lint` on PRs that touch messages.json.
`Rust advisories` stays outside the gate.
cargo-deny's advisories check can fail on an unchanged tree as soon as a
new RustSec advisory is published, which blocks unrelated PRs and keeps
the Rust lint jobs from being made required. Split it out:
- `deny` now checks bans, licenses and sources only, and stays in the
Rust lint matrix.
- A new `advisories` check runs in its own `Rust advisories` job on
ubuntu-24.04, outside the `Rust lint` gate.
* refactor(dirt): move vault-health data layer to libs/common
* refactor(dirt): update CipherHealthView imports to @bitwarden/common
* feat(browser): move health tab to OSS build
* refactor(browser): reorganize health components into subdirectories
* remove old codeowners entry
* move files to apps/browser/src/dirt/health/popup/ refactor token out of code and move into healthaccessservice instead
* fix import errors
* fix feature flag
* move cipherhealthview into shared dirt models
* update more imports
---------
Co-authored-by: Leslie Tilton <23057410+Banrion@users.noreply.github.com>
Only the OSS variant of macos-package-mas was uploaded, so the commercial
build couldn't be tested through TestFlight. Both variants share the
com.bitwarden.desktop app and the same build number. The commercial build
now gets a ".1" suffix so App Store Connect doesn't reject it as a
duplicate.
* [BRE-2234] Use beta-specific provisioning profiles for macOS beta desktop build
The macOS beta desktop build signed with the stable app's Developer ID
provisioning profiles and shipped an appId that had no matching App ID
registered in the Apple Developer portal.
BRE-2234 registered beta its own identifiers, App Group and provisioning
profiles, so point the beta build at them:
- macos-beta job downloads and installs the beta profiles
- electron-builder.beta.json references the beta Developer ID profile
- appId changes to com.bitwarden.beta.desktop to match the new identifier
The beta profiles are already uploaded to the bitwardenci/profiles
container. Stable jobs are untouched.
* ci: Add entitlements file for beta build
---------
Co-authored-by: Isaiah Inuwa <iinuwa@bitwarden.com>
* [BRE-2234] Use channel-named provisioning profile blobs for stable macOS jobs
The stable macOS jobs download provisioning profiles under names that
don't say which channel they belong to, and one carries a year that no
longer matches its contents:
bitwarden_desktop_appstore
bitwarden_desktop_developer_id
bitwarden_desktop_autofill_app_store_2024
bitwarden_desktop_autofill_developer_id
Switch to channel-explicit names, matching the bitwarden_beta_desktop_*
set already in use:
bitwarden_stable_desktop_appstore
bitwarden_stable_desktop_developer_id
bitwarden_stable_desktop_autofill_appstore
bitwarden_stable_desktop_autofill_developer_id
The blobs are already uploaded and hold the same profiles as the names
they replace, so this is a rename at the reference site only. The legacy
blobs stay in place until this lands, then get removed.
Touches macos-build, macos-package-github and macos-package-mas.
macos-beta is handled separately in #23703.
* Update electron-builder and masdev profile references to match
The workflow copies each profile into apps/desktop/ under its blob
filename, and electron-builder resolves it by that name. Renaming the
blobs without updating these would leave the mac and mas sections
pointing at files that no longer exist.
Caught in review by @iinuwa.
Every Renovate lock-file-maintenance run moves napi-derive-backend to
5.1.x, which breaks desktop_native against the exact napi "=3.8.5" pin:
5.1.x emits bindgen_prelude calls missing from napi 3.8.5.
Pin napi-derive-backend to an exact version napi 3.8.5 supports so
lock-file maintenance can't move it. Remove this pin once napi itself
is upgraded past 3.8.5.