4.9.63

CHANGELOG.md

@@ -1,3 +1,9 @@
+## 4.9.63 (Apr 10, 2023)
+
+- Site toggle panel (detect dark theme and shortcut).
+- App toggle panel (automation and shortcut).
+- Improved Site List indexing.
+
 ## 4.9.62 (Jan 8, 2023)
 
 - Fixed a edge case with extracting color numbers, it's now able to extract `rgb(0 0 0/0.04)`. (#10565)

README.md

@@ -45,9 +45,9 @@ Please note that if you encounter error `Too many open files (os error 24)`, the
 
 Prior to publication, extension stores provide digital signatures for extensions. These digital signatures certify the integrity of the archive (that extension bundle did not get corrupted or bit-rotted) and that extension store preformed very basic extension validation.
 
-Dark Reader repository contains these digital signatures and you can add them to the extension bundle. The following will build Dark Reader for Firefox version 4.9.62:
+Dark Reader repository contains these digital signatures and you can add them to the extension bundle. The following will build Dark Reader for Firefox version 4.9.63:
 ```
-npm run build -- --firefox --version=4.9.62
+npm run build -- --firefox --version=4.9.63
 ```
 
 Please note that only Firefox Add-ons store signatures are present in the repositiry right now. Also, due to NodeJS and TypeScript version compatibility, one might have to first check out the old revision (commit), then build the extension files, then check out the recent commit and create the bundle (by running only `signature` and `zip` steps).

package.json

@@ -1,6 +1,6 @@
 {
   "name": "darkreader",
-  "version": "4.9.62",
+  "version": "4.9.63",
   "description": "Dark mode for every website",
   "scripts": {
     "api": "node --max-old-space-size=3072 tasks/cli.js build --api",

src/manifest.json

@@ -1,7 +1,7 @@
 {
     "manifest_version": 2,
     "name": "Dark Reader",
-    "version": "4.9.62",
+    "version": "4.9.63",
     "author": "Alexander Shutau",
     "description": "__MSG_extension_description__",
     "default_locale": "en",

tasks/cli.js

@@ -88,7 +88,7 @@ async function ensureGitClean() {
  * dependencies which is identical to already published version serves as a proof
  * that the published version was always free of (now known) vulnerabilities.
  *
- * @param {string} version The desired git version, e.g., 'v4.9.62' or 'v4.9.37.1'
+ * @param {string} version The desired git version, e.g., 'v4.9.63' or 'v4.9.37.1'
  * @param {boolean} fixVulnerabilities Whether of not to attempt to fix known vulnerabilities
  */
 async function checkoutVersion(version, fixVulnerabilities) {