[PR #5821] [PM-25396] Publish store builds when release branches are updated #6070

New Issue

2025-11-27T00:19:25-06:00

GiteaMirror commented

2025-11-27 00:19:25 -06:00

Original Pull Request: https://github.com/bitwarden/android/pull/5821

State: closed
Merged: Yes

🎟️ Tracking

PM-25396

📔 Objective

While handling the release process our team noticed builds in Firebase that weren't published to PlayStore, this PR addresses that.

Our QA team noted something similar previously happened when distribution inputs were missed while triggering manual builds, changing the input defaults too while at it so there's less of a chance of release process disruption.

⏰ 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

**Original Pull Request:** https://github.com/bitwarden/android/pull/5821 **State:** closed **Merged:** Yes --- ## 🎟️ Tracking PM-25396 ## 📔 Objective While handling the release process our team noticed builds in Firebase that weren't published to PlayStore, this PR addresses that. Our QA team noted something similar previously happened when distribution inputs were missed while triggering manual builds, changing the input defaults too while at it so there's less of a chance of release process disruption. ## ⏰ 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

GiteaMirror added the pull-request label 2025-11-27 00:19:25 -06:00

GiteaMirror closed this issue