Skip to content

[Targeting] Windows launch-on-login - #16433

Merged
aminomancer merged 1 commit into
mainfrom
aminomancer/issue16432
Jul 27, 2026
Merged

[Targeting] Windows launch-on-login#16433
aminomancer merged 1 commit into
mainfrom
aminomancer/issue16432

Conversation

@aminomancer

Copy link
Copy Markdown
Member

Fixes #16432

@aminomancer

Copy link
Copy Markdown
Member Author

I'm not sure why the tests are complaining about this one, since it's existed for quite some time. The other one is new and just landed in Nightly.

@jaredlockhart

Copy link
Copy Markdown
Collaborator

@aminomancer

Copy link
Copy Markdown
Member Author

@jaredlockhart Thanks, I've added a patch for this. We'll try to remember that in the future.

Is this required by the Nimbus client to even do the client-side targeting, or is it only required for these tests to pass? I'm looking at the code in RemoteSettingsExperimentLoader, and it seems like it's just directly using ASRouterTargeting for targeting.

This targeting config is intended for an experiment that would target 153.0.1 (the dot release). So I'm wondering whether we need to uplift that patch I linked. It doesn't seem like it, but it would be good to confirm.

If Experimenter only cares what's on Nightly, then we shouldn't need to uplift it. But maybe Experimenter will throw an error if we combine a min version of 153.0.1 with an advanced targeting config that uses attributes that only exist on 155, and then I guess we'd need to uplift the attributes.

@jaredlockhart

Copy link
Copy Markdown
Collaborator

@aminomancer Perfect here it is:

https://github.com/mozilla/experimenter/pull/16470/changes#diff-b1f24c02bf0792a736219641270854bf2706698f595e0599018d0446ece2c7c9

And yes so right now only Experimenter is validating against that list but soon desktop will soon as well so better to get it all in place now rather than getting caught out when the client makes the switch.

After the above lands we can update this and it should be passing 🙏

@jaredlockhart

Copy link
Copy Markdown
Collaborator

@aminomancer Okay all tidied up, I'll mark it as blocked so it doesn't get accidentally merged until you're ready.

@aminomancer
aminomancer force-pushed the aminomancer/issue16432 branch from cc88aac to 34ad1d1 Compare July 27, 2026 22:10
@aminomancer
aminomancer enabled auto-merge July 27, 2026 22:38
@aminomancer
aminomancer force-pushed the aminomancer/issue16432 branch from 4927cdd to babb0f6 Compare July 27, 2026 22:44
@aminomancer
aminomancer added this pull request to the merge queue Jul 27, 2026
Merged via the queue into main with commit 27c3fd2 Jul 27, 2026
30 checks passed
@aminomancer
aminomancer deleted the aminomancer/issue16432 branch July 27, 2026 23:42
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.

[Targeting]

3 participants