From 741a76d664f133c3af4f388c060b834b54dbf157 Mon Sep 17 00:00:00 2001
From: "riseproject-dev[bot]"
 <330740410+riseproject-dev[bot]@users.noreply.github.com>
Date: Wed, 30 Sep 2026 08:09:32 +0000
Subject: [PATCH 1/2] liteparse: Add version 2.15.0

Signed-off-by: riseproject-dev[bot] <330740410+riseproject-dev[bot]@users.noreply.github.com>
---
 docs/packages/liteparse.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/packages/liteparse.yaml b/docs/packages/liteparse.yaml
index 478b016ed4d..a395d5e8131 100644
--- a/docs/packages/liteparse.yaml
+++ b/docs/packages/liteparse.yaml
@@ -44,3 +44,4 @@ versions:
   - filename: liteparse-2.14.7-cp310-abi3-manylinux_2_39_riscv64.whl
     sha256: 7338747b81d7c0ddf10d4dbba5affc14af235435a9575d501ebcd5b476cc0a04
     requires-python: '>=3.10'
+- version: 2.15.0

From 4cf65160ffb146194184641c7d94120bcc45be76 Mon Sep 17 00:00:00 2001
From: Ludovic Henry <git@ludovic.dev>
Date: Thu, 1 Oct 2026 08:44:41 +0000
Subject: [PATCH 2/2] liteparse: carry forward riscv64 patch(es) to 2.15.0

The nightly-upgrade bot bumped docs/packages/liteparse.yaml to 2.15.0 without
creating a matching patches/liteparse/2.15.0/ directory, so the workflow's
unconditional 'git apply .../*.patch' step failed with no matching file.
Carrying forward the same patch(es) from 2.14.7/ unchanged; CI will
confirm they still apply cleanly against the new upstream version.
---
 .../0001-skia-accept-riscv64-target-cpu.patch | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
 create mode 100644 patches/liteparse/2.15.0/0001-skia-accept-riscv64-target-cpu.patch

diff --git a/patches/liteparse/2.15.0/0001-skia-accept-riscv64-target-cpu.patch b/patches/liteparse/2.15.0/0001-skia-accept-riscv64-target-cpu.patch
new file mode 100644
index 00000000000..aaa74eb2ecd
--- /dev/null
+++ b/patches/liteparse/2.15.0/0001-skia-accept-riscv64-target-cpu.patch
@@ -0,0 +1,19 @@
+Upstream-Status: To upstream [not yet submitted; pdfium main's skia/BUILD.gn still lacks the riscv64 branch Chromium's copy has]
+
+PDFium's skia/BUILD.gn asserts on every target CPU its skia_opts chain does not
+name, so `gn gen` fails for target_cpu = "riscv64" even with pdf_use_skia=false:
+the root BUILD.gn's gn_check group depends on //skia whenever checkout_skia is set,
+which it is for checkout_configuration=small. Chromium's own skia/BUILD.gn already
+carries this empty riscv64 branch (Skia's portable code path needs no extra flags).
+diff --git a/skia/BUILD.gn b/skia/BUILD.gn
+--- a/skia/BUILD.gn
++++ b/skia/BUILD.gn
+@@ -560,6 +560,8 @@ skia_source_set("skia_opts") {
+     # Conditional and empty body needed to avoid assert below
+   } else if (current_cpu == "mipsel" || current_cpu == "mips64el") {
+     cflags += [ "-fomit-frame-pointer" ]
++  } else if (current_cpu == "riscv64") {
++    # Conditional and empty body needed to avoid assert() below.
+   } else {
+     assert(false, "Unsupported target CPU " + current_cpu)
+   }