Skip to content

ci(android): adopt staged Play rollout - #372

Merged
dkhalife merged 1 commit into
mainfrom
dkhalife-adopt-play-rollout
Aug 3, 2026
Merged

ci(android): adopt staged Play rollout#372
dkhalife merged 1 commit into
mainfrom
dkhalife-adopt-play-rollout

Conversation

@dkhalife

@dkhalife dkhalife commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

Adopts the centrally managed staged Google Play rollout for Android.

Copilot AI review requested due to automatic review settings August 3, 2026 03:27

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adopts a centrally managed (template-driven) staged Google Play rollout configuration for the Android Azure DevOps pipeline by delegating rollout settings to the shared template.

Changes:

  • Removes explicit environment: canary from the Android release stage template context.
  • Removes explicit track: internal from the Play Store release job template context.
Show a summary per file
File Description
.azuredevops/android-build.yml Updates the Android Play Store release stage/job context to rely on centrally managed staged rollout defaults.

Review details

  • Files reviewed: 1/1 changed files
  • Comments generated: 1
  • Review effort level: Lite

Comment thread .azuredevops/android-build.yml
@dkhalife
dkhalife merged commit 76014cb into main Aug 3, 2026
10 checks passed
@dkhalife
dkhalife deleted the dkhalife-adopt-play-rollout branch August 3, 2026 03:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants