chrome-types 0.1.415 → 0.1.417

package/_all.d.ts

@@ -14,8 +14,8 @@
  * limitations under the License.
  */
 
-// Generated on Thu Jan 29 2026 22:38:22 GMT+0000 (Coordinated Universal Time)
-// Built at 0c1cfac406a9571eeeaa7f69773ac1e40cc4573d
+// Generated on Tue Feb 24 2026 22:27:22 GMT+0000 (Coordinated Universal Time)
+// Built at 0bad8d6a9bf042d660f069e9eae4ad5debee3aaa
 
 // Includes all types, including MV2 + Platform Apps APIs.
 
@@ -12428,7 +12428,7 @@ declare namespace chrome {
       /**
        * Implements the WebCrypto's [SubtleCrypto](https://www.w3.org/TR/WebCryptoAPI/#subtlecrypto-interface) interface. The cryptographic operations, including key generation, are hardware-backed.
        *
-       * Only non-extractable keys can be generated. The supported key types are RSASSA-PKCS1-V1\_5 and RSA-OAEP (on Chrome versions 135+) with `modulusLength` up to 2048 and ECDSA with `namedCurve` P-256. Each RSASSA-PKCS1-V1\_5 and ECDSA key can be used for signing data at most once, unless the extension is allowlisted through the [KeyPermissions policy](https://chromeenterprise.google/policies/#KeyPermissions), in which case the key can be used indefinitely. RSA-OAEP keys are supported since Chrome version 135 and can be used by extensions allowlisted through that same policy to unwrap other keys.
+       * Only non-extractable keys can be generated. The supported key types are RSASSA-PKCS1-V1\_5 with `modulusLength` up to 2048 and ECDSA with `namedCurve` P-256. Each key can be used for signing data at most once, unless the extension is allowlisted by the [KeyPermissions policy](https://chromeenterprise.google/policies/#KeyPermissions), in which case the key can be used indefinitely.
        *
        * Keys generated on a specific `Token` cannot be used with any other Tokens, nor can they be used with `window.crypto.subtle`. Equally, `Key` objects created with `window.crypto.subtle` cannot be used with this interface.
        */
@@ -12437,7 +12437,7 @@ declare namespace chrome {
       /**
        * Implements the WebCrypto's [SubtleCrypto](https://www.w3.org/TR/WebCryptoAPI/#subtlecrypto-interface) interface. The cryptographic operations, including key generation, are software-backed. Protection of the keys, and thus implementation of the non-extractable property, is done in software, so the keys are less protected than hardware-backed keys.
        *
-       * Only non-extractable keys can be generated. The supported key types are RSASSA-PKCS1-V1\_5 and RSA-OAEP (on Chrome versions 135+) with `modulusLength` up to 2048. Each RSASSA-PKCS1-V1\_5 key can be used for signing data at most once, unless the extension is allowlisted through the [KeyPermissions policy](https://chromeenterprise.google/policies/#KeyPermissions), in which case the key can be used indefinitely. RSA-OAEP keys are supported since Chrome version 135 and can be used by extensions allowlisted through that same policy to unwrap other keys.
+       * Only non-extractable keys can be generated. The only supported key type is RSASSA-PKCS1-V1\_5 with `modulusLength` up to 2048. Each key can be used for signing data at most once, unless the extension is allowlisted through the [KeyPermissions policy](https://chromeenterprise.google/policies/#KeyPermissions), in which case the key can be used indefinitely.
        *
        * Keys generated on a specific `Token` cannot be used with any other Tokens, nor can they be used with `window.crypto.subtle`. Equally, `Key` objects created with `window.crypto.subtle` cannot be used with this interface.
        *
@@ -29490,10 +29490,6 @@ declare namespace chrome {
    * Use the `system.display` API to query display metadata.
    *
    * @chrome-permission system.display
-   * @chrome-platform chromeos
-   * @chrome-platform linux
-   * @chrome-platform mac
-   * @chrome-platform win
    */
   export namespace system.display {
 

package/index.d.ts

@@ -14,8 +14,8 @@
  * limitations under the License.
  */
 
-// Generated on Thu Jan 29 2026 22:38:17 GMT+0000 (Coordinated Universal Time)
-// Built at 0c1cfac406a9571eeeaa7f69773ac1e40cc4573d
+// Generated on Tue Feb 24 2026 22:27:18 GMT+0000 (Coordinated Universal Time)
+// Built at 0bad8d6a9bf042d660f069e9eae4ad5debee3aaa
 
 // Includes MV3+ APIs only.
 
@@ -8616,7 +8616,7 @@ declare namespace chrome {
       /**
        * Implements the WebCrypto's [SubtleCrypto](https://www.w3.org/TR/WebCryptoAPI/#subtlecrypto-interface) interface. The cryptographic operations, including key generation, are hardware-backed.
        *
-       * Only non-extractable keys can be generated. The supported key types are RSASSA-PKCS1-V1\_5 and RSA-OAEP (on Chrome versions 135+) with `modulusLength` up to 2048 and ECDSA with `namedCurve` P-256. Each RSASSA-PKCS1-V1\_5 and ECDSA key can be used for signing data at most once, unless the extension is allowlisted through the [KeyPermissions policy](https://chromeenterprise.google/policies/#KeyPermissions), in which case the key can be used indefinitely. RSA-OAEP keys are supported since Chrome version 135 and can be used by extensions allowlisted through that same policy to unwrap other keys.
+       * Only non-extractable keys can be generated. The supported key types are RSASSA-PKCS1-V1\_5 with `modulusLength` up to 2048 and ECDSA with `namedCurve` P-256. Each key can be used for signing data at most once, unless the extension is allowlisted by the [KeyPermissions policy](https://chromeenterprise.google/policies/#KeyPermissions), in which case the key can be used indefinitely.
        *
        * Keys generated on a specific `Token` cannot be used with any other Tokens, nor can they be used with `window.crypto.subtle`. Equally, `Key` objects created with `window.crypto.subtle` cannot be used with this interface.
        */
@@ -8625,7 +8625,7 @@ declare namespace chrome {
       /**
        * Implements the WebCrypto's [SubtleCrypto](https://www.w3.org/TR/WebCryptoAPI/#subtlecrypto-interface) interface. The cryptographic operations, including key generation, are software-backed. Protection of the keys, and thus implementation of the non-extractable property, is done in software, so the keys are less protected than hardware-backed keys.
        *
-       * Only non-extractable keys can be generated. The supported key types are RSASSA-PKCS1-V1\_5 and RSA-OAEP (on Chrome versions 135+) with `modulusLength` up to 2048. Each RSASSA-PKCS1-V1\_5 key can be used for signing data at most once, unless the extension is allowlisted through the [KeyPermissions policy](https://chromeenterprise.google/policies/#KeyPermissions), in which case the key can be used indefinitely. RSA-OAEP keys are supported since Chrome version 135 and can be used by extensions allowlisted through that same policy to unwrap other keys.
+       * Only non-extractable keys can be generated. The only supported key type is RSASSA-PKCS1-V1\_5 with `modulusLength` up to 2048. Each key can be used for signing data at most once, unless the extension is allowlisted through the [KeyPermissions policy](https://chromeenterprise.google/policies/#KeyPermissions), in which case the key can be used indefinitely.
        *
        * Keys generated on a specific `Token` cannot be used with any other Tokens, nor can they be used with `window.crypto.subtle`. Equally, `Key` objects created with `window.crypto.subtle` cannot be used with this interface.
        *
@@ -20782,10 +20782,6 @@ declare namespace chrome {
    * Use the `system.display` API to query display metadata.
    *
    * @chrome-permission system.display
-   * @chrome-platform chromeos
-   * @chrome-platform linux
-   * @chrome-platform mac
-   * @chrome-platform win
    */
   export namespace system.display {
 

package/package.json

@@ -5,7 +5,7 @@
   "type": "module",
   "name": "chrome-types",
   "config": {
-    "build-hash": "177c6b60247436db"
+    "build-hash": "1bb01ecec127038a"
   },
   "repository": {
     "type": "git",
@@ -16,5 +16,5 @@
     "url": "https://github.com/GoogleChrome/chrome-types/issues"
   },
   "homepage": "https://github.com/GoogleChrome/chrome-types",
-  "version": "0.1.415"
+  "version": "0.1.417"
 }