Add minimum version to extension management

components/policy/resources/policy_templates.json

Index: components/policy/resources/policy_templates.json
diff --git a/components/policy/resources/policy_templates.json b/components/policy/resources/policy_templates.json
index 3859d6889ab2a2d75e9f3b9ce316a1c6bf50ccff..d2dd3af9411ef154d3f382e216e899daf5870c05 100644
--- a/components/policy/resources/policy_templates.json
+++ b/components/policy/resources/policy_templates.json
@@ -1761,6 +1761,10 @@
                   'allowed_permissions': {
                     '$ref': 'ListOfPermissions',
                   },
+                  'minimum_version': {
+                    'type': 'string',
+                    'pattern': '^[0-9]+([.][0-9]+)*$',
+                  },
                 },
               },
               '^update_url:': {
@@ -1810,6 +1814,7 @@
             'abcdefghijklmnopabcdefghijklmnop' : {
               'installation_mode': 'allowed',
               'blocked_permissions': ['history'],
+              'minimum_version': '1.0.1',
             },
             'bcdefghijklmnopabcdefghijklmnopa' : {
               'installation_mode': 'force_installed',
@@ -1850,6 +1855,8 @@
 
           "allowed_permissions": similar to "blocked_permissions", but instead explicitly allow some permissions which might be blocked by global blocked permission list, thus can not be configured for "*" extension. Note that this setting doesn't give granted permissions to extensions automatically.
 
+          "minimum_version": maps to a version string. The format of the version string is the same as the one used in extension manifest, as described at <ph name="LINK_TO_EXTENSION_DOC4">https://developer.chrome.com/apps/manifest/version</ph>. Extension with version older than the specified minimum version will be disabled. This applies to force-installed extensions as well.
+
           The following settings can be used only for the default "*" configuration:
 
           "install_sources": Each item in this list is an extension-style match pattern (see https://developer.chrome.com/extensions/match_patterns). Users will be able to easily install items from any URL that matches an item in this list. Both the location of the *.crx file and the page where the download is started from (i.e.  the referrer) must be allowed by these patterns.