[trmartin4]

🎟️ Tracking

PM-46111

📔 Objective

Add a "🚩 Flags removed" category to the generated release notes for PRs labeled t:flagged-code-removal. Without it, those PRs fall through to "🎨 Other".

The category sits below Maintenance and above Dependency Updates. Cleanup PRs carry only this t: label, so no earlier category claims them.

This will allow feature flag removals (which unlock features for self-hosted customers) to be categorized independently in release notes. Note that this is indicating the removal of flagged code and not the feature flag itself, which must remain in place for backward compatibility.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.82%. Comparing base (262dba3) to head (d63b7b4).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7551   +/-   ##
=======================================
  Coverage   86.82%   86.82%           
=======================================
  Files         896      896           
  Lines       65792    65792           
  Branches     9407     9407           
=======================================
  Hits        57121    57121           
  Misses       5187     5187           
  Partials     3484     3484           

Flag	Coverage Δ
app-data	18.69% <ø> (ø)
app-ui-auth-tools	18.62% <ø> (ø)
app-ui-platform	16.47% <ø> (ø)
app-ui-vault	26.97% <ø> (ø)
authenticator	6.02% <ø> (ø)
lib-core-network-bridge	4.12% <ø> (ø)
lib-data-ui	1.25% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 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]

🤖 Bitwarden Claude Code Review

Overall Assessment: APPROVE

This PR adds a 🚩 Flags removed category to .github/release.yml for PRs labeled t:flagged-code-removal. It sits between Maintenance and Dependency Updates. GitHub assigns each PR to the first category that matches, and sdlc-enforce-labels.yml requires exactly one t:* label per PR, so these PRs will land in the new category instead of falling through to 🎨 Other. The YAML structure matches the categories around it, and no in-repo documentation describes the release-note categories.

[vvolkgang]

Reviewed in the iOS repo: bitwarden/ios#3177 (review)