Skip to content

fix: automatic progressive releases#5219

Merged
Lukewh merged 2 commits intomainfrom
lukewh/automatic-progression
Jul 16, 2025
Merged

fix: automatic progressive releases#5219
Lukewh merged 2 commits intomainfrom
lukewh/automatic-progression

Conversation

@Lukewh
Copy link
Copy Markdown
Contributor

@Lukewh Lukewh commented Jul 16, 2025

Done

If a progressive release has been marked as "automatic" an explicit release is not created, therefore we need to:

  1. Check the current release against the channel map (like we do to get the up-to-date percentage of current users.
  2. Update the percentage of the release if the channel map has a different percentage
  3. if the progressive release has "finished" the percentage in the channel map will be null, in this case set the percentage to 100.

How to QA

Testing

  • This PR has tests - covered by current tests
  • No testing required (explain why):

Issue / Card

Fixes https://warthogs.atlassian.net/browse/WD-23858

Screenshots

@webteam-app
Copy link
Copy Markdown

Copy link
Copy Markdown
Contributor

@ilayda-cp ilayda-cp left a comment

Choose a reason for hiding this comment

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

🚀

@Lukewh Lukewh merged commit ac90f4b into main Jul 16, 2025
12 of 13 checks passed
@Lukewh Lukewh deleted the lukewh/automatic-progression branch July 16, 2025 12:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants