Bug 2052250 - add support for re-enrolling into rollouts - #7466
Merged
freshstrangemusic merged 1 commit intoJul 8, 2026
Merged
Conversation
freshstrangemusic
self-requested a review
July 8, 2026 16:03
freshstrangemusic
approved these changes
Jul 8, 2026
freshstrangemusic
enabled auto-merge
July 8, 2026 16:07
jonesetc
pushed a commit
to jonesetc/application-services
that referenced
this pull request
Aug 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
updates Nimbus enrollment evolution to support re enabled rollouts with the same slug. If a rollout reappears after ending (pausing) and the client only has a previous WasEnrolled tombstone, the SDK now evaluates it like a new rollout instead of treating it as an internal error
Pull Request checklist
[ci full]to the PR title.