Merge branch 'develop' into dev/opds-authentication

.eslintrc.js

@@ -59,6 +59,12 @@ module.exports = {
         "eol-last": ["error", "always"],
         semi: ["error", "always"],
 
+        // eslint-disable-next-line @typescript-eslint/no-empty-object-type
+        "@typescript-eslint/no-empty-object-type": 0,
+
+        "@typescript-eslint/prefer-promise-reject-errors": 0,
+        "@typescript-eslint/only-throw-error": 0,
+
         "@typescript-eslint/no-unsafe-member-access": 0,
         "@typescript-eslint/no-unsafe-return": 0,
         "@typescript-eslint/no-unsafe-assignment": 0,

.github/workflows/main.yml

@@ -156,7 +156,7 @@ jobs:
     #- run: npm install @octokit/rest
     - name: GitHub Tagged Release Delete/ReCreate and Upload Build Artefacts
       if: ${{ github.event_name != 'pull_request' }}
-      run: node scripts/release-github.js
+      run: node scripts/release-github.mjs
     # - name: Upload Artifact
     #   if: ${{ github.event_name != 'pull_request' }}
     #   uses: actions/upload-artifact@v2

.gitignore

@@ -3,4 +3,5 @@ dist
 release
 node_modules
 .DS_Store
+lcp.node
 external-assets/*

.npmignore

@@ -1,2 +1,6 @@
+.history
+release
 node_modules
 .DS_Store
+lcp.node
+external-assets/*

README.md

@@ -91,6 +91,12 @@ we used `proxy-agent` package from `TooTallNate` (https://github.com/TooTallNate
 
 see https://www.npmjs.com/package/proxy-from-env#environment-variables for more information.
 
+## LCP support in Thorium Reader
+
+Thorium Reader supports LCP-protected publications via an additional software component which is not available in this open-source codebase. When Thorium Reader is compiled from the open-source code without the additional production-grade library, the application can only load publications protected with the LCP "Basic Encryption Profile". For example, licenses generated by the open-source LCP server written in Go, without the patch that enables production-grade LCP Encryption Profiles.
+
+In order to create a production-grade LCP-compliant variant / derivation of Thorium Reader (known as a "fork"), additional confidential software components and processes must be integrated in the custom application's build / release workflow. This represents a non-trivial amount of time and effort, as well as close collaboration between the fork's development team and EDRLab's technical staff. To cover operational costs, EDRLab charges a maintenance fee. Feel free to contact EDRlab to discuss your requirements.
+
 ## Command line
 
 ```

latest.json

@@ -1,7 +1,7 @@
 {
     "id": "io.github.edrlab.thorium",
-    "version": "2.4.1",
-    "date": "2024-03-22T00:00:00.000Z",
+    "version": "3.0.0",
+    "date": "2024-06-26T00:00:00.000Z",
     "url": "https://thorium.edrlab.org",
-    "url_": "https://github.com/edrlab/thorium-reader/releases/tag/v2.4.1"
+    "url_": "https://github.com/edrlab/thorium-reader/releases/tag/v3.0.0"
 }