Just landed on google3: https://critique.corp.google.com/#review/200100370

[Auto-generated comment by a script] We noticed that this issue is targeted for M-67; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-67 label, otherwise remove Merge-TBD label. Thanks.

No merge needed, and updating milestone since change actually affects M-68.

Needed to revert the CL in #1, will reland eventually.

[Auto-generated comment by a script] We noticed that this issue is targeted for M-68; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-68 label, otherwise remove Merge-TBD label. Thanks.

No merge needed, not a client change.

We need to reland this playstore change when M-68 goes to 100%.  I have the google3 change ready but not sent for review yet (https://critique.corp.google.com/#review/201432576).

I think the time is quickly approaching to push this CL.  Estelle, I'll double-check that it's ready to land.  Let me know when to submit.

The CL on google3 has been sent for review, will submit upon approval -- https://critique.corp.google.com/#review/206177490

Estelle, I don't want to jump the gun (again) but I'm thinking that we should enable this Playstore change now, since we're starting to roll out M-68 Stable on Android.  What do you think?

cmasso@, just checking again to see if we need to wait for this playstore update for 100% of stable, and if that has not yet happened.

Landed on google3: https://critique.corp.google.com/#review/207949486

[Auto-generated comment by a script] We noticed that this issue is targeted for M-68; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-68 label, otherwise remove Merge-TBD label. Thanks.

No merge needed.