Update starting milestone for HttpsUpgradesEnabled policy

This policy was backported to M112 in crrev.com/c/4307550, so this updates the `supported_on` field to start at M112 on ToT as well. Bug: 1420809 Change-Id: I30e3140e9cae9d9482561086baa81940f42b0328 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4307738 Auto-Submit: Chris Thompson <[email protected]> Reviewed-by: Alexander Hendrich <[email protected]> Commit-Queue: Alexander Hendrich <[email protected]> Cr-Commit-Position: refs/heads/main@{#1112999}
Igalia · Mar 3, 2023 · 7a13c0f · 7a13c0f
1 parent 90a47c1
commit 7a13c0f
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/...nts/policy/resources/templates/policy_definitions/Miscellaneous/HttpsUpgradesEnabled.yaml b/...nts/policy/resources/templates/policy_definitions/Miscellaneous/HttpsUpgradesEnabled.yaml
@@ -17,10 +17,10 @@ desc: |-
   See also the <ph name="HTTPS_ONLY_MODE_POLICY_NAME">HttpsOnlyMode</ph> policy.
 
 supported_on:
-- android:113-
-- chrome.*:113-
-- chrome_os:113-
-- fuchsia:113-
+- android:112-
+- chrome.*:112-
+- chrome_os:112-
+- fuchsia:112-
 
 features:
   dynamic_refresh: true