BRE-1355 - Rename Bitwarden Unified to Bitwarden Lite

[vgrassia]

🎟️ Tracking

• BRE-1355

📔 Objective

Bitwarden Unified is now Bitwarden Lite. This PR renames the relevant parts in the code base.

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[claude]

Claude finished @vgrassia's task —— View job

---

Code Review Complete

• Evaluate PR title and description
• Review all changed files
• Search for missed "Unified" references
• Check test coverage implications
• Verify documentation updates
• Provide comprehensive findings

---

Summary

This PR successfully renames "Bitwarden Unified" to "Bitwarden Lite" across the codebase. The changes are straightforward and consistent, touching GitHub templates, workflows, and core settings.

Findings

Finding 1: Clean rename implementation

👍 The rename is executed consistently across all relevant files:

• Issue template renamed and updated (bw-unified.yml → bw-lite.yml)
• Workflow files updated for both job names and comments
• Property renamed in both implementation and interface (GlobalSettings.cs and IGlobalSettings.cs)
• Usage updated in service collection extensions

Finding 2: No test coverage for LiteDeployment property

💭 The LiteDeployment property (formerly UnifiedDeployment) has no associated unit tests. While this isn't introduced by this PR, consider adding tests to verify the property's behavior in different deployment scenarios, particularly given its usage in ServiceCollectionExtensions.cs:648 where it controls proxy configuration logic.

Suggested test structure

[Theory]
[InlineData(true, true)]  // Lite deployment should skip nginx proxy check
[InlineData(false, false)] // Non-lite should attempt nginx proxy check
public void LiteDeployment_AffectsProxyConfiguration(bool isLite, bool shouldCheckNginx)
{
    // Test that LiteDeployment correctly influences proxy behavior
}

Finding 3: PR title and description quality

👍 The PR follows proper conventions:

• Clear, descriptive title with ticket reference
• Objective explains both what changed and why
• Jira ticket properly linked
• Checklist completed appropriately

Good Practices Observed

• Consistent naming across all file types (YAML, C#)
• Both interface and implementation updated together
• Comments in workflow files updated alongside code changes

Test Plan

⚠️ The PR checklist indicates new unit/integration tests were written "where applicable," but given this is a pure rename with no behavior changes, the lack of new tests is reasonable. However, consider verifying:

1. Manual testing with LiteDeployment=true to ensure proxy configuration works as expected
2. Running the updated workflow (build-bitwarden-lite.yml) to confirm it triggers correctly

Action Items

None blocking for merge. The rename is complete and correct.

---

[codecov]

Codecov Report

❌ Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 53.06%. Comparing base (75d8250) to head (71a22f9).
⚠️ Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
...SharedWeb/Utilities/ServiceCollectionExtensions.cs	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6592      +/-   ##
==========================================
- Coverage   53.10%   53.06%   -0.04%     
==========================================
  Files        1913     1913              
  Lines       85280    85276       -4     
  Branches     7635     7635              
==========================================
- Hits        45289    45254      -35     
- Misses      38232    38272      +40     
+ Partials     1759     1750       -9     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

Checkmarx One – Scan Summary & Details – 892ddb12-12c1-4d9b-aa51-e965ffc1eb78

Great job! No new security vulnerabilities introduced in this pull request

[djsmith85]

Re-assured with @vgrassia that migration docs will be provided to update the setting LiteDeployment before booting up the container, since renaming a setting is usually bad.