Release 2.20.1

fix: fallback to timestamp in case if crypto context is not available
Previous tests have been done in either secure (HTTPS) or loopback (localhost) environments, so I missed the case, that crypto methods might not be available Fixes #159
2026-04-07 11:03:37 +00:00 · 2026-03-13 17:06:27 +02:00 · 2026-03-13 17:05:48 +02:00 · 2026-03-13 17:05:04 +02:00
5 changed files with 5 additions and 5 deletions
--- a/frontend/package.json
+++ b/frontend/package.json
@@ -2,7 +2,7 @@
    "name": "ahriman-frontend",
    "private": true,
    "type": "module",
-    "version": "2.20.0",
+    "version": "2.20.1",
    "scripts": {
        "build": "tsc && vite build",
        "dev": "vite",
--- a/frontend/src/api/client/Client.ts
+++ b/frontend/src/api/client/Client.ts
@@ -40,7 +40,7 @@ export class Client {

        const headers: Record<string, string> = {
            Accept: "application/json",
-            "X-Request-ID": crypto.randomUUID(),
+            "X-Request-ID": crypto.randomUUID?.() ?? Date.now().toString(),
        };
        if (json !== undefined) {
            headers["Content-Type"] = "application/json";
--- a/package/archlinux/PKGBUILD
+++ b/package/archlinux/PKGBUILD
@@ -2,7 +2,7 @@

 pkgbase='ahriman'
 pkgname=('ahriman' 'ahriman-core' 'ahriman-triggers' 'ahriman-web')
-pkgver=2.20.0
+pkgver=2.20.1
 pkgrel=1
 pkgdesc="ArcH linux ReposItory MANager"
 arch=('any')
--- a/package/share/man/man1/ahriman.1
+++ b/package/share/man/man1/ahriman.1
@@ -1,4 +1,4 @@
-.TH AHRIMAN "1" "2026\-03\-08" "ahriman 2.20.0" "ArcH linux ReposItory MANager"
+.TH AHRIMAN "1" "2026\-03\-13" "ahriman 2.20.1" "ArcH linux ReposItory MANager"
 .SH NAME
 ahriman \- ArcH linux ReposItory MANager
 .SH SYNOPSIS
--- a/src/ahriman/init.py
+++ b/src/ahriman/init.py
@@ -17,4 +17,4 @@
 # You should have received a copy of the GNU General Public License
 # along with this program. If not, see <http://www.gnu.org/licenses/>.
 #
-__version__ = "2.20.0"
+__version__ = "2.20.1"
Author	SHA1	Message	Date
Evgenii Alekseev	d99b61d8c0	Release 2.20.1	2026-03-13 17:06:27 +02:00
Evgenii Alekseev	34d0b8cf73	fix: fallback to timestamp in case if crypto context is not available Previous tests have been done in either secure (HTTPS) or loopback (localhost) environments, so I missed the case, that crypto methods might not be available Fixes #159	2026-03-13 17:05:48 +02:00
Evgenii Alekseev	cc082dbd6f	feat: add dark theme support and increase contrast	2026-03-13 17:05:04 +02:00