Stirling-PDF

mirror of https://github.com/Stirling-Tools/Stirling-PDF.git synced 2026-09-03 05:10:16 +03:00

Author	SHA1	Message	Date
Anthony Stirling	40d180d665	Merge main into fix_ex_20260720	2026-08-21 07:29:57 +01:00
stirlingbot[bot]	e092b487ec	Update Backend 3rd Party Licenses (#7608 ) Auto-generated by stirlingbot[bot] This PR updates the backend license report based on dependency changes. Signed-off-by: stirlingbot[bot] <stirlingbot[bot]@users.noreply.github.com> Co-authored-by: stirlingbot[bot] <195170888+stirlingbot[bot]@users.noreply.github.com>	2026-08-20 21:38:26 +00:00
dependabot[bot]	a7c6fa6ef6	build(deps): bump io.swagger.core.v3:swagger-core-jakarta from 2.2.46 to 2.2.53 (#7526 ) Bumps io.swagger.core.v3:swagger-core-jakarta from 2.2.46 to 2.2.53. [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=io.swagger.core.v3:swagger-core-jakarta&package-manager=gradle&previous-version=2.2.46&new-version=2.2.53)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2026-08-20 21:29:49 +00:00
brios	4e5b1102b6	refactor(search): improve TextInput clear button styling and add component unit tests (#7578 ) # Description of Changes FIxes minor stylistic problem about the search bar. Mainly the X and the spacing on the result's icons vs text. ### New <img width="1594" height="600" alt="image" src="https://github.com/user-attachments/assets/f3710cad-f1a6-4aa1-9c2a-f3f474fd2dd6" /> ### Old <img width="1584" height="618" alt="image" src="https://github.com/user-attachments/assets/2d9c26a8-2d68-4d86-9d51-b12f90b17fe0" /> <!-- Please provide a summary of the changes, including: - What was changed - Why the change was made - Any challenges encountered Closes #(issue_number) --> --- ## Checklist ### General - [X] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [X] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [X] I have performed a self-review of my own code - [X] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [X] I have run `task check` to verify linters, typechecks, and tests pass - [X] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-20 21:21:50 +00:00
dependabot[bot]	b3acdc4aab	build(deps): bump actions/setup-java from 5.2.0 to 5.7.0 (#7530 ) Bumps [actions/setup-java](https://github.com/actions/setup-java) from 5.2.0 to 5.7.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions/setup-java/releases">actions/setup-java's releases</a>.</em></p> <blockquote> <h2>v5.7.0</h2> <h2>What's Changed</h2> <ul> <li>Fix npm audit failures on releases/v5 by <a href="https://github.com/brunoborges"><code>@brunoborges</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/1154">actions/setup-java#1154</a></li> <li>Backport <a href="https://redirect.github.com/actions/setup-java/issues/1151">#1151</a>: Fix missing wrapper cache distributions by <a href="https://github.com/brunoborges"><code>@brunoborges</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/1153">actions/setup-java#1153</a></li> <li>Deprecate legacy Adopt distributions in v5 by <a href="https://github.com/brunoborges"><code>@brunoborges</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/1186">actions/setup-java#1186</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/setup-java/compare/v5.6.0...v5.7.0">https://github.com/actions/setup-java/compare/v5.6.0...v5.7.0</a></p> <h2>v5.6.0</h2> <h2>What's Changed</h2> <ul> <li>Backport to v5: Add Maven compiler problem matcher for javac diagnostics by <a href="https://github.com/brunoborges"><code>@brunoborges</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/1087">actions/setup-java#1087</a></li> <li>feat: expose cache-primary-key output (<a href="https://redirect.github.com/actions/setup-java/issues/597">#597</a>) [v5 backport] by <a href="https://github.com/brunoborges"><code>@brunoborges</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/1089">actions/setup-java#1089</a></li> <li>dist: Cover Tencent Kona JDK 25 (<a href="https://redirect.github.com/actions/setup-java/issues/1108">#1108</a>) [v5 backport] by <a href="https://github.com/brunoborges"><code>@brunoborges</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/1110">actions/setup-java#1110</a></li> <li>Backport <a href="https://redirect.github.com/actions/setup-java/issues/1111">#1111</a>: Preserve Maven toolchains across repeated setup-java runs (<a href="https://redirect.github.com/actions/setup-java/issues/1099">#1099</a>) by <a href="https://github.com/brunoborges"><code>@brunoborges</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/1113">actions/setup-java#1113</a></li> <li>Backport <a href="https://redirect.github.com/actions/setup-java/issues/1097">#1097</a>/<a href="https://redirect.github.com/actions/setup-java/issues/1098">#1098</a> to v5: cache Maven and Gradle wrapper distributions separately by <a href="https://github.com/brunoborges"><code>@brunoborges</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/1122">actions/setup-java#1122</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/setup-java/compare/v5...v5.6.0">https://github.com/actions/setup-java/compare/v5...v5.6.0</a></p> <h2>v5.5.0</h2> <h2>What's Changed</h2> <ul> <li>chore: enforce pre-PR validation (aggregate scripts, git hooks, PR checklist) by <a href="https://github.com/brunoborges"><code>@brunoborges</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/1061">actions/setup-java#1061</a></li> <li>Bump github/codeql-action from 3 to 4 by <a href="https://github.com/dependabot"><code>@dependabot</code></a>[bot] in <a href="https://redirect.github.com/actions/setup-java/pull/1069">actions/setup-java#1069</a></li> <li>Bump actions/checkout from 6 to 7 by <a href="https://github.com/dependabot"><code>@dependabot</code></a>[bot] in <a href="https://redirect.github.com/actions/setup-java/pull/1068">actions/setup-java#1068</a></li> <li>Bump actions/setup-python from 5 to 6 by <a href="https://github.com/dependabot"><code>@dependabot</code></a>[bot] in <a href="https://redirect.github.com/actions/setup-java/pull/1067">actions/setup-java#1067</a></li> <li>Bump <code>@typescript-eslint/parser</code> from 8.61.1 to 8.62.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a>[bot] in <a href="https://redirect.github.com/actions/setup-java/pull/1062">actions/setup-java#1062</a></li> <li>feat: Add verify-signature plumbing and Temurin+Microsoft verification support by <a href="https://github.com/johnoliver"><code>@johnoliver</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/1060">actions/setup-java#1060</a></li> <li>Updated jetbrains test: https.request() now catches errors. This fixes leaking tests as well by <a href="https://github.com/jmjaffe37"><code>@jmjaffe37</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/1070">actions/setup-java#1070</a></li> <li>Fix arm64 e2e workflow tests mislabeled as x64 by <a href="https://github.com/brunoborges"><code>@brunoborges</code></a> with <a href="https://github.com/Copilot"><code>@Copilot</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/1073">actions/setup-java#1073</a></li> <li>feat: suppress Maven transfer progress via MAVEN_ARGS by default (add show-download-progress input) by <a href="https://github.com/brunoborges"><code>@brunoborges</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/1053">actions/setup-java#1053</a></li> <li>feat: Disable interactiveMode in generated Maven settings.xml by <a href="https://github.com/brunoborges"><code>@brunoborges</code></a> with <a href="https://github.com/Copilot"><code>@Copilot</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/1052">actions/setup-java#1052</a></li> <li>Bump prettier from 3.6.2 to 3.9.1 by <a href="https://github.com/dependabot"><code>@dependabot</code></a>[bot] in <a href="https://redirect.github.com/actions/setup-java/pull/1066">actions/setup-java#1066</a></li> <li>chore(deps-dev): bump eslint-plugin-jest from 29.0.1 to 29.15.4 by <a href="https://github.com/dependabot"><code>@dependabot</code></a>[bot] in <a href="https://redirect.github.com/actions/setup-java/pull/1074">actions/setup-java#1074</a></li> <li>fix: Maven Toolchains grows unexpectedly by <a href="https://github.com/Okeanos"><code>@Okeanos</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/534">actions/setup-java#534</a></li> <li>dist: Support Tencent Kona JDK by <a href="https://github.com/johnshajiang"><code>@johnshajiang</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/672">actions/setup-java#672</a></li> <li>feat: Add set-default option by <a href="https://github.com/gsmet"><code>@gsmet</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/1017">actions/setup-java#1017</a></li> <li>docs: document problem matcher (and how to disable it), Maven Wrapper caching, and generated interactiveMode by <a href="https://github.com/brunoborges"><code>@brunoborges</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/1075">actions/setup-java#1075</a></li> <li>feat: Add distribution detection support to .sdkmanrc file by <a href="https://github.com/lukaszgyg"><code>@lukaszgyg</code></a> in <a href="https://redirect.github.com/actions/setup-java/pull/975">actions/setup-java#975</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/jmjaffe37"><code>@jmjaffe37</code></a> made their first contribution in <a href="https://redirect.github.com/actions/setup-java/pull/1070">actions/setup-java#1070</a></li> <li><a href="https://github.com/gsmet"><code>@gsmet</code></a> made their first contribution in <a href="https://redirect.github.com/actions/setup-java/pull/1017">actions/setup-java#1017</a></li> <li><a href="https://github.com/lukaszgyg"><code>@lukaszgyg</code></a> made their first contribution in <a href="https://redirect.github.com/actions/setup-java/pull/975">actions/setup-java#975</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/setup-java/compare/v5...v5.5.0">https://github.com/actions/setup-java/compare/v5...v5.5.0</a></p> <h2>v5.4.0</h2> <h2>What's Changed</h2> <ul> <li>Bump <code>@typescript-eslint/parser</code> from 8.48.0 to 8.61.1 by <a href="https://github.com/dependabot"><code>@dependabot</code></a>[bot] in <a href="https://redirect.github.com/actions/setup-java/pull/1021">actions/setup-java#1021</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/actions/setup-java/commit/b6effb05e454b25005698d916606bdc6ffcbf961"><code>b6effb0</code></a> Deprecate legacy Adopt distributions in v5 (<a href="https://redirect.github.com/actions/setup-java/issues/1186">#1186</a>)</li> <li><a href="https://github.com/actions/setup-java/commit/e498d2a66a953492f322542257b22125c989b422"><code>e498d2a</code></a> Backport <a href="https://redirect.github.com/actions/setup-java/issues/1151">#1151</a>: Fix missing wrapper cache distributions (<a href="https://redirect.github.com/actions/setup-java/issues/1153">#1153</a>)</li> <li><a href="https://github.com/actions/setup-java/commit/6a3384db745932178632d0e22b2bd28cad1678e6"><code>6a3384d</code></a> Fix npm audit failures on releases/v5 (<a href="https://redirect.github.com/actions/setup-java/issues/1154">#1154</a>)</li> <li><a href="https://github.com/actions/setup-java/commit/03ad4de0992f5dab5e18fcb136590ce7c4a0ac95"><code>03ad4de</code></a> Backport <a href="https://redirect.github.com/actions/setup-java/issues/1097">#1097</a>/<a href="https://redirect.github.com/actions/setup-java/issues/1098">#1098</a>: cache Maven and Gradle wrapper distributions separately...</li> <li><a href="https://github.com/actions/setup-java/commit/d229d2e858d9137cc0b3f118fa5184b9f0a44ac4"><code>d229d2e</code></a> Backport <a href="https://redirect.github.com/actions/setup-java/issues/1111">#1111</a>: Preserve Maven toolchains across repeated setup-java runs (<a href="https://redirect.github.com/actions/setup-java/issues/1">#1</a>...</li> <li><a href="https://github.com/actions/setup-java/commit/bbf0f6967066506f72571a96d5d6c67ca42ab460"><code>bbf0f69</code></a> dist: Cover Tencent Kona JDK 25 (<a href="https://redirect.github.com/actions/setup-java/issues/1110">#1110</a>)</li> <li><a href="https://github.com/actions/setup-java/commit/513edc4f8710565e4ad696f3b7d8e3bda584a46c"><code>513edc4</code></a> feat: expose cache-primary-key output (<a href="https://redirect.github.com/actions/setup-java/issues/597">#597</a>) [v5 backport] (<a href="https://redirect.github.com/actions/setup-java/issues/1089">#1089</a>)</li> <li><a href="https://github.com/actions/setup-java/commit/62df799a9c6e3022bb466697c66c36e9a2dbf347"><code>62df799</code></a> Add Maven compiler problem matcher for javac diagnostics (<a href="https://redirect.github.com/actions/setup-java/issues/1087">#1087</a>)</li> <li><a href="https://github.com/actions/setup-java/commit/176156a187714aaf460b0a3c8f21e8b4f784b978"><code>176156a</code></a> chore: bump version to 5.6.0 for v5 release line</li> <li><a href="https://github.com/actions/setup-java/commit/bf7b8deac240b9cee05eb15ccdb1d2f424a54b9f"><code>bf7b8de</code></a> build: rebuild dist for backported changes (<a href="https://redirect.github.com/actions/setup-java/issues/1079">#1079</a>, <a href="https://redirect.github.com/actions/setup-java/issues/1083">#1083</a>, <a href="https://redirect.github.com/actions/setup-java/issues/1084">#1084</a>)</li> <li>Additional commits viewable in <a href="https://github.com/actions/setup-java/compare/v5.2.0...b6effb05e454b25005698d916606bdc6ffcbf961">compare view</a></li> </ul> </details> <br /> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2026-08-20 21:10:12 +00:00
dependabot[bot]	b549964529	build(deps-dev): bump fpdf2 from 2.8.7 to 2.8.8 in /engine (#7560 ) Bumps [fpdf2](https://github.com/py-pdf/fpdf2) from 2.8.7 to 2.8.8. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/py-pdf/fpdf2/releases">fpdf2's releases</a>.</em></p> <blockquote> <h2>Add resource access controls, SVG complexity limits, Optional Content Groups, and other features and bug fixes</h2> <h2>[2.8.8] - 2026-08-09</h2> <blockquote> <p>[!WARNING] Upgrading to <strong>fpdf2 2.8.8</strong> is strongly recommended for applications that render user-provided images, SVGs, or HTML content.</p> </blockquote> <h3>Added</h3> <ul> <li>Punjabi (pa) tutorial translation - thanks to <a href="https://github.com/Pawansingh3889"><code>@Pawansingh3889</code></a></li> <li><code>FPDF.svg_limits</code> and <code>SVGLimits</code> to configure SVG complexity limits while rendering SVG images</li> <li><code>resource_access_policy</code> and <a href="https://py-pdf.github.io/fpdf2/Security.html">Security considerations</a> documentation</li> <li><a href="https://py-pdf.github.io/fpdf2/OptionalContent.html"><code>FPDF.optional_content()</code></a> context manager to mark content as visible on screen only or in print only, using PDF Optional Content Groups - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/441">#441</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/441">py-pdf/fpdf2#441</a>), based on a recipe by <a href="https://github.com/digidigital"><code>@digidigital</code></a> - thanks to <a href="https://github.com/eugen-goebel"><code>@eugen-goebel</code></a></li> <li>basic support for SVG <code><symbol></code> elements in the SVG parser - thanks to <a href="https://github.com/Theo1335"><code>@Theo1335</code></a></li> <li>basic support for SVG <code><switch></code> elements in the SVG parser - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/537">#537</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/537">py-pdf/fpdf2#537</a>) - thanks to <a href="https://github.com/dannymaaz"><code>@dannymaaz</code></a></li> <li>support for keeping aspect ratio for images in templates - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1118">#1118</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1118">py-pdf/fpdf2#1118</a>) - thanks to <a href="https://github.com/prateek-dagar"><code>@prateek-dagar</code></a></li> </ul> <h3>Fixed</h3> <ul> <li>custom height passed to <code>Paragraph.ln()</code> in a text region is now applied to the line it terminates instead of the first line of the following paragraph - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1786">#1786</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1786">py-pdf/fpdf2#1786</a>) - thanks to <a href="https://github.com/Sanjays2402"><code>@Sanjays2402</code></a></li> <li>the optional <code>numpy</code> import in <code>image_parsing.py</code> no longer crashes on CPUs unsupported by numpy's <code>manylinux</code> wheel baseline; <code>RuntimeError</code> is now treated the same as <code>ImportError</code>, so <code>numpy</code> degrades to unavailable instead of taking down <code>import fpdf</code> - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1908">#1908</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1908">py-pdf/fpdf2#1908</a>) - thanks to <a href="https://github.com/stumpylog"><code>@stumpylog</code></a></li> <li>font state (family, style, size, current font, and the page-level "font is set" flag) no longer leaks back onto the <code>FPDF</code> instance after a <code>text_columns()</code> / <code>text_region()</code> context exits, so a subsequent <code>pdf.cell()</code> / <code>pdf.write()</code> renders at the caller's font instead of the last paragraph's - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1804">#1804</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1804">py-pdf/fpdf2#1804</a>) - thanks to <a href="https://github.com/Pawansingh3889"><code>@Pawansingh3889</code></a></li> <li>text rendering when the first text on a page starts with a fallback glyph - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1772">#1772</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1772">py-pdf/fpdf2#1772</a>)</li> <li>preserve boundary-neutral formatting during bidirectional text preprocessing - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1779">#1779</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1779">py-pdf/fpdf2#1779</a>)</li> <li>transform application on user space gradients - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1784">#1784</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1784">py-pdf/fpdf2#1784</a>)</li> <li>dependency extras for camelot-py and endesive on pyproject.toml - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1792">#1792</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1792">py-pdf/fpdf2#1792</a>)</li> <li>preserve link annotations during dry-run of <code>FPDF.multi_cell</code> - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1807">#1807</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1807">py-pdf/fpdf2#1807</a>) - thanks to <a href="https://github.com/CoLa5"><code>@CoLa5</code></a></li> <li>preserve two consecutive markdown links (without space inbetween) - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1814">#1814</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1814">py-pdf/fpdf2#1814</a>) - thanks to <a href="https://github.com/CoLa5"><code>@CoLa5</code></a></li> <li>support markdown style around markdown links - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1826">#1826</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1826">py-pdf/fpdf2#1826</a>) - thanks to <a href="https://github.com/CoLa5"><code>@CoLa5</code></a></li> <li>Reset gstate for ToC-rendering - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1837">#1837</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1837">py-pdf/fpdf2#1837</a>) - thanks to <a href="https://github.com/CoLa5"><code>@CoLa5</code></a></li> <li>preserve markdown format in <code>FPDF.multi_cell</code> in dry-run - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1840">#1840</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1840">py-pdf/fpdf2#1840</a>) - thanks to <a href="https://github.com/CoLa5"><code>@CoLa5</code></a></li> <li>fix page order after dry-run of <code>FPDF.multi_cell</code> in ToC - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1836">#1836</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1836">py-pdf/fpdf2#1836</a>) - thanks to <a href="https://github.com/CoLa5"><code>@CoLa5</code></a></li> <li>rendering SVG arcs with very small sweeps that previously rounded to zero - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1831">#1831</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1831">py-pdf/fpdf2#1831</a>)</li> <li>spurious "Not enough horizontal space to render a single character" error when text without break opportunities is split into many small fragments, e.g. by a fallback font alternating with the main font - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1250">#1250</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1250">py-pdf/fpdf2#1250</a>) - thanks to <a href="https://github.com/uttam12331"><code>@uttam12331</code></a></li> <li>number of surviving escape characters - <strong>cf.</strong> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1215">#1215</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1215">py-pdf/fpdf2#1215</a>) - thanks to <a href="https://github.com/amidou-naba"><code>@amidou-naba</code></a></li> <li>leading spaces on new lines inside <code><pre></code> and <code><pre><code></code> blocks are no longer dropped - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1063">#1063</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1063">py-pdf/fpdf2#1063</a>) - thanks to <a href="https://github.com/eugen-goebel"><code>@eugen-goebel</code></a></li> <li><code>FPDF.set_font()</code> can restore <code>current_font</code> when the selected font state diverged - <em>cf.</em> [PR <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1872">#1872</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/pull/1872">py-pdf/fpdf2#1872</a>) - thanks to <a href="https://github.com/gaoflow"><code>@gaoflow</code></a></li> <li>embed CID-keyed CFF fonts as raw CFF programs so browser PDF viewers render them correctly - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1874">#1874</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1874">py-pdf/fpdf2#1874</a>)</li> <li>fixed broken links on documentation not directly leading to the API reference - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1876">#1876</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1876">py-pdf/fpdf2#1876</a>) - thanks to <a href="https://github.com/iamfazakb"><code>@iamfazakb</code></a></li> <li>reject SVG <code><use></code> cycles and excessive nested expansion to prevent resource exhaustion in <code>FPDF.image()</code></li> <li>count SVG <code><switch></code> elements in SVG complexity limits</li> <li>declare the default base state and display order for Optional Content Groups so PDF viewers can list layers correctly - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1895">#1895</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1895">py-pdf/fpdf2#1895</a>)</li> </ul> <h3>Changed</h3> <ul> <li>skip byte-for-byte compressed data comparison when zlib-ng is detected, regardless of OS</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/py-pdf/fpdf2/blob/master/CHANGELOG.md">fpdf2's changelog</a>.</em></p> <blockquote> <h2>[2.8.8] - 2026-08-09</h2> <h3>Added</h3> <ul> <li>Punjabi (pa) tutorial translation - thanks to <a href="https://github.com/Pawansingh3889"><code>@Pawansingh3889</code></a></li> <li><code>FPDF.svg_limits</code> and <code>SVGLimits</code> to configure SVG complexity limits while rendering SVG images</li> <li><code>resource_access_policy</code> and <a href="https://py-pdf.github.io/fpdf2/Security.html">Security considerations</a> documentation</li> <li><a href="https://py-pdf.github.io/fpdf2/OptionalContent.html"><code>FPDF.optional_content()</code></a> context manager to mark content as visible on screen only or in print only, using PDF Optional Content Groups - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/441">#441</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/441">py-pdf/fpdf2#441</a>), based on a recipe by <a href="https://github.com/digidigital"><code>@digidigital</code></a> - thanks to <a href="https://github.com/eugen-goebel"><code>@eugen-goebel</code></a></li> <li>basic support for SVG <code><symbol></code> elements in the SVG parser - thanks to <a href="https://github.com/Theo1335"><code>@Theo1335</code></a></li> <li>basic support for SVG <code><switch></code> elements in the SVG parser - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/537">#537</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/537">py-pdf/fpdf2#537</a>) - thanks to <a href="https://github.com/dannymaaz"><code>@dannymaaz</code></a></li> <li>support for keeping aspect ratio for images in templates - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1118">#1118</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1118">py-pdf/fpdf2#1118</a>) - thanks to <a href="https://github.com/prateek-dagar"><code>@prateek-dagar</code></a></li> </ul> <h3>Fixed</h3> <ul> <li>custom height passed to <code>Paragraph.ln()</code> in a text region is now applied to the line it terminates instead of the first line of the following paragraph - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1786">#1786</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1786">py-pdf/fpdf2#1786</a>) - thanks to <a href="https://github.com/Sanjays2402"><code>@Sanjays2402</code></a></li> <li>the optional <code>numpy</code> import in <code>image_parsing.py</code> no longer crashes on CPUs unsupported by numpy's <code>manylinux</code> wheel baseline; <code>RuntimeError</code> is now treated the same as <code>ImportError</code>, so <code>numpy</code> degrades to unavailable instead of taking down <code>import fpdf</code> - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1908">#1908</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1908">py-pdf/fpdf2#1908</a>) - thanks to <a href="https://github.com/stumpylog"><code>@stumpylog</code></a></li> <li>font state (family, style, size, current font, and the page-level "font is set" flag) no longer leaks back onto the <code>FPDF</code> instance after a <code>text_columns()</code> / <code>text_region()</code> context exits, so a subsequent <code>pdf.cell()</code> / <code>pdf.write()</code> renders at the caller's font instead of the last paragraph's - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1804">#1804</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1804">py-pdf/fpdf2#1804</a>) - thanks to <a href="https://github.com/Pawansingh3889"><code>@Pawansingh3889</code></a></li> <li>text rendering when the first text on a page starts with a fallback glyph - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1772">#1772</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1772">py-pdf/fpdf2#1772</a>)</li> <li>preserve boundary-neutral formatting during bidirectional text preprocessing - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1779">#1779</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1779">py-pdf/fpdf2#1779</a>)</li> <li>transform application on user space gradients - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1784">#1784</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1784">py-pdf/fpdf2#1784</a>)</li> <li>dependency extras for camelot-py and endesive on pyproject.toml - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1792">#1792</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1792">py-pdf/fpdf2#1792</a>)</li> <li>preserve link annotations during dry-run of <code>FPDF.multi_cell</code> - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1807">#1807</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1807">py-pdf/fpdf2#1807</a>) - thanks to <a href="https://github.com/CoLa5"><code>@CoLa5</code></a></li> <li>preserve two consecutive markdown links (without space inbetween) - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1814">#1814</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1814">py-pdf/fpdf2#1814</a>) - thanks to <a href="https://github.com/CoLa5"><code>@CoLa5</code></a></li> <li>support markdown style around markdown links - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1826">#1826</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1826">py-pdf/fpdf2#1826</a>) - thanks to <a href="https://github.com/CoLa5"><code>@CoLa5</code></a></li> <li>Reset gstate for ToC-rendering - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1837">#1837</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1837">py-pdf/fpdf2#1837</a>) - thanks to <a href="https://github.com/CoLa5"><code>@CoLa5</code></a></li> <li>preserve markdown format in <code>FPDF.multi_cell</code> in dry-run - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1840">#1840</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1840">py-pdf/fpdf2#1840</a>) - thanks to <a href="https://github.com/CoLa5"><code>@CoLa5</code></a></li> <li>fix page order after dry-run of <code>FPDF.multi_cell</code> in ToC - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1836">#1836</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1836">py-pdf/fpdf2#1836</a>) - thanks to <a href="https://github.com/CoLa5"><code>@CoLa5</code></a></li> <li>rendering SVG arcs with very small sweeps that previously rounded to zero - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1831">#1831</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1831">py-pdf/fpdf2#1831</a>)</li> <li>spurious "Not enough horizontal space to render a single character" error when text without break opportunities is split into many small fragments, e.g. by a fallback font alternating with the main font - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1250">#1250</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1250">py-pdf/fpdf2#1250</a>) - thanks to <a href="https://github.com/uttam12331"><code>@uttam12331</code></a></li> <li>number of surviving escape characters - <strong>cf.</strong> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1215">#1215</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1215">py-pdf/fpdf2#1215</a>) - thanks to <a href="https://github.com/amidou-naba"><code>@amidou-naba</code></a></li> <li>leading spaces on new lines inside <code><pre></code> and <code><pre><code></code> blocks are no longer dropped - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1063">#1063</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1063">py-pdf/fpdf2#1063</a>) - thanks to <a href="https://github.com/eugen-goebel"><code>@eugen-goebel</code></a></li> <li><code>FPDF.set_font()</code> can restore <code>current_font</code> when the selected font state diverged - <em>cf.</em> [PR <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1872">#1872</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/pull/1872">py-pdf/fpdf2#1872</a>) - thanks to <a href="https://github.com/gaoflow"><code>@gaoflow</code></a></li> <li>embed CID-keyed CFF fonts as raw CFF programs so browser PDF viewers render them correctly - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1874">#1874</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1874">py-pdf/fpdf2#1874</a>)</li> <li>fixed broken links on documentation not directly leading to the API reference - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1876">#1876</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1876">py-pdf/fpdf2#1876</a>) - thanks to <a href="https://github.com/iamfazakb"><code>@iamfazakb</code></a></li> <li>reject SVG <code><use></code> cycles and excessive nested expansion to prevent resource exhaustion in <code>FPDF.image()</code></li> <li>count SVG <code><switch></code> elements in SVG complexity limits</li> <li>declare the default base state and display order for Optional Content Groups so PDF viewers can list layers correctly - <em>cf.</em> [issue <a href="https://redirect.github.com/py-pdf/fpdf2/issues/1895">#1895</a>](<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1895">py-pdf/fpdf2#1895</a>)</li> </ul> <h3>Changed</h3> <ul> <li>skip byte-for-byte compressed data comparison when zlib-ng is detected, regardless of OS</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/py-pdf/fpdf2/commit/e1fc653d8fce65d2fb118755bda8581a9bf1e4d9"><code>e1fc653</code></a> release v2.8.8 (<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1916">#1916</a>)</li> <li><a href="https://github.com/py-pdf/fpdf2/commit/42ec66442bf278b9768ca787fe601d3d334c62e4"><code>42ec664</code></a> add Sanjays2402 as a contributor for code (<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1915">#1915</a>)</li> <li><a href="https://github.com/py-pdf/fpdf2/commit/af9d7dc11c36db49364c0096ad1edca5d569c676"><code>af9d7dc</code></a> fix(text_region): apply Paragraph.ln(h) height to the line it terminates (<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1904">#1904</a>)</li> <li><a href="https://github.com/py-pdf/fpdf2/commit/81951f837b46782df38f7c4d6f4c8f2644ac9b7e"><code>81951f8</code></a> add stumpylog as a contributor for bug, and code (<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1913">#1913</a>)</li> <li><a href="https://github.com/py-pdf/fpdf2/commit/b30c38c8cfc804342f429fffb26cc44f34f20af3"><code>b30c38c</code></a> Fix: catch RuntimeError alongside ImportError for the optional numpy import (...</li> <li><a href="https://github.com/py-pdf/fpdf2/commit/63df0d0f4f085d3a014166d2d752d9c1e77305e4"><code>63df0d0</code></a> Update github/codeql-action action to v4.37.6 (<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1910">#1910</a>)</li> <li><a href="https://github.com/py-pdf/fpdf2/commit/11a30e672cad2157b657642ed290cb27eb57e482"><code>11a30e6</code></a> Update crate-ci/typos action to v1.49.0 (<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1911">#1911</a>)</li> <li><a href="https://github.com/py-pdf/fpdf2/commit/f65707b369a7ca7aaa6226a77eabf69b9903eac4"><code>f65707b</code></a> Update step-security/harden-runner action to v2.20.1 (<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1912">#1912</a>)</li> <li><a href="https://github.com/py-pdf/fpdf2/commit/a7f7c8945139fb5a20d1993fcff6484b5c2267c7"><code>a7f7c89</code></a> Update github/codeql-action action to v4.37.4 (<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1907">#1907</a>)</li> <li><a href="https://github.com/py-pdf/fpdf2/commit/fe9d8f52643c5dcb88370813f51c29410463e299"><code>fe9d8f5</code></a> Update pypa/gh-action-pypi-publish action to v1.14.2 (<a href="https://redirect.github.com/py-pdf/fpdf2/issues/1906">#1906</a>)</li> <li>Additional commits viewable in <a href="https://github.com/py-pdf/fpdf2/compare/2.8.7...2.8.8">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=fpdf2&package-manager=uv&previous-version=2.8.7&new-version=2.8.8)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2026-08-20 21:10:05 +00:00
github-actions[bot]andLudy87	8e3ecb1fe4	chore: update Gradle to 9.7.1 (#7607 ) Automated update of the Gradle wrapper and Gradle Docker build images. Gradle version: `9.7.1` Docker image: `gradle:9.7.1-jdk25` Co-authored-by: Ludy87 <4592558+Ludy87@users.noreply.github.com>	2026-08-20 20:46:50 +00:00
Ludy	cb0cafabd9	ci: Extract Gradle cache priming into a reusable workflow (#7572 ) # Description of Changes - What was changed - Moved the `gradle-cache-prime` job from `build.yml` into a dedicated reusable workflow. - Added `workflow_call` support for invocation from other workflows. - Added a `push` trigger for the `main` branch. - Updated `build.yml` to call the new reusable workflow. - Why the change was made - Keeps the shared Gradle cache warm after changes are pushed to `main`. - Allows pull request builds to reuse the same cache and reduce dependency resolution time. - Separates cache maintenance from the main build workflow. --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have run `task check` to verify linters, typechecks, and tests pass - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-20 20:03:54 +00:00
stirlingbot[bot]	90d39aec0b	🌐 Sync Translations + Update README Progress Table (#7583 ) ### Description of Changes This Pull Request was automatically generated to synchronize updates to translation files and documentation. Below are the details of the changes made: #### 1. Synchronization of Translation Files - Updated translation files (`frontend/editor/public/locales//translation.toml`) to reflect changes in the reference file `en-US/translation.toml`. - Ensured consistency and synchronization across all supported language files. - Highlighted any missing or incomplete translations. - Format: TOML #### 2. Update README.md* - Generated the translation progress table in `README.md` using `counter_translation_v3.py`. - Added a summary of the current translation status for all supported languages. - Included up-to-date statistics on translation coverage. #### Why these changes are necessary - Keeps translation files aligned with the latest reference updates. - Ensures the documentation reflects the current translation progress. --- Auto-generated by [create-pull-request][1]. [1]: https://github.com/peter-evans/create-pull-request Co-authored-by: stirlingbot[bot] <195170888+stirlingbot[bot]@users.noreply.github.com>	2026-08-20 19:44:56 +00:00
Ludy	6376d1ff8b	ci: share Docker base image across test-build matrix (#7584 ) # Description of Changes This PR decouples the Docker base-image preparation from the embedded Docker image matrix builds in `.github/workflows/test-build-docker.yml`. - Added a dedicated `prepare-base-image` job that runs once when a pull request changes the Docker base image. - Builds `stirling-pdf-base:pr-test` once for `linux/amd64` instead of rebuilding the same image independently in every matrix job. - Exports the prepared image with `docker save`, compresses it, and uploads it as a short-lived GitHub Actions artifact. - Added a dependency from `test-build-docker-images` to `prepare-base-image`, while still allowing the matrix job to run when base-image preparation is skipped. - Each matrix entry downloads and loads the prepared Docker image when `docker-base-changed` is enabled. - Removed the previous per-matrix `Build base image locally` step. - Keeps the prepared image available to the embedded Docker builds through the local Docker daemon. The change was made to eliminate redundant base-image builds across the Docker test matrix. Previously, pull requests modifying `docker/base` caused each matrix entry to build the identical base image independently and in parallel. Preparing the image once reduces duplicated CI work, improves consistency between matrix entries, and should reduce CI resource usage and execution time for Docker-related pull requests. --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have run `task check` to verify linters, typechecks, and tests pass - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-20 19:43:33 +00:00
dependabot[bot]	b8cfde3a7a	build(deps): bump imageioVersion from 3.13.1 to 3.14.0 (#7598 ) Bumps `imageioVersion` from 3.13.1 to 3.14.0. Updates `com.twelvemonkeys.imageio:imageio-batik` from 3.13.1 to 3.14.0 Updates `com.twelvemonkeys.imageio:imageio-bmp` from 3.13.1 to 3.14.0 Updates `com.twelvemonkeys.imageio:imageio-jpeg` from 3.13.1 to 3.14.0 Updates `com.twelvemonkeys.imageio:imageio-tiff` from 3.13.1 to 3.14.0 Updates `com.twelvemonkeys.imageio:imageio-webp` from 3.13.1 to 3.14.0 Updates `com.twelvemonkeys.imageio:imageio-psd` from 3.13.1 to 3.14.0 Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2026-08-20 19:42:11 +00:00
dependabot[bot]	43f7db0234	build(deps): bump github/codeql-action/upload-sarif from 4.37.6 to 4.37.7 (#7591 ) Bumps [github/codeql-action/upload-sarif](https://github.com/github/codeql-action) from 4.37.6 to 4.37.7. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/github/codeql-action/releases">github/codeql-action/upload-sarif's releases</a>.</em></p> <blockquote> <h2>v4.37.7</h2> <ul> <li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.3">2.26.3</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4085">#4085</a></li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/github/codeql-action/blob/main/CHANGELOG.md">github/codeql-action/upload-sarif's changelog</a>.</em></p> <blockquote> <h1>CodeQL Action Changelog</h1> <p>See the <a href="https://github.com/github/codeql-action/releases">releases page</a> for the relevant changes to the CodeQL CLI and language packs.</p> <h2>[UNRELEASED]</h2> <p>No user facing changes.</p> <h2>4.37.7 - 13 Aug 2026</h2> <ul> <li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.3">2.26.3</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4085">#4085</a></li> </ul> <h2>4.37.6 - 04 Aug 2026</h2> <ul> <li>Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to <code>.github/codeql-config.yml</code> to align it with the suggested path that is used elsewhere. <a href="https://redirect.github.com/github/codeql-action/pull/4070">#4070</a></li> </ul> <h2>4.37.5 - 03 Aug 2026</h2> <ul> <li>Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the <code>init</code> Action instead of falling back to downloading the bundle before extracting it. <a href="https://redirect.github.com/github/codeql-action/pull/4061">#4061</a></li> </ul> <h2>4.37.4 - 29 Jul 2026</h2> <ul> <li>This version of the CodeQL Action adds support for the <code>tools</code> input for the <code>codeql-action/init</code> step to be specified using a <code>github-codeql-tools</code> <a href="https://docs.github.com/en/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization">repository property</a>. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to <code>toolcache</code> to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for <code>tools</code> in the workflow definition always takes precedence unless the value of the repository property starts with <code>!</code>. <a href="https://redirect.github.com/github/codeql-action/pull/4037">#4037</a></li> <li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.2">2.26.2</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4051">#4051</a></li> </ul> <h2>4.37.3 - 22 Jul 2026</h2> <p>No user facing changes.</p> <h2>4.37.2 - 21 Jul 2026</h2> <ul> <li>The new address format for the <code>config-file</code> input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the <code>remote=</code> prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. <a href="https://redirect.github.com/github/codeql-action/pull/4023">#4023</a></li> <li>The CodeQL Action can now make use of <a href="https://docs.github.com/en/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries">configured private registries</a> in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. <a href="https://redirect.github.com/github/codeql-action/pull/4007">#4007</a></li> </ul> <h2>4.37.1 - 16 Jul 2026</h2> <ul> <li><em>Upcoming breaking change</em>: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. <a href="https://redirect.github.com/github/codeql-action/pull/3956">#3956</a></li> <li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.1">2.26.1</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4019">#4019</a></li> </ul> <h2>4.37.0 - 08 Jul 2026</h2> <ul> <li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.0">2.26.0</a>. <a href="https://redirect.github.com/github/codeql-action/pull/3995">#3995</a></li> <li>In addition to the existing input format, the <code>config-file</code> input for the <code>codeql-action/init</code> step will soon support a new <code>[owner/]repo[@ref][:path]</code> format. All components except the repository name are optional. If omitted, <code>owner</code> defaults to the same owner as the repository the analysis is running for, <code>ref</code> to <code>main</code>, and <code>path</code> to <code>.github/codeql-action.yaml</code>. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. <a href="https://redirect.github.com/github/codeql-action/pull/3973">#3973</a></li> </ul> <h2>4.36.3 - 01 Jul 2026</h2> <p>No user facing changes.</p> <h2>4.36.2 - 04 Jun 2026</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/github/codeql-action/commit/ff2f1c621b7f889edc0d3c761ac2e6a3f8cdb0dd"><code>ff2f1c6</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4093">#4093</a> from github/update-v4.37.7-be7a3dbb8</li> <li><a href="https://github.com/github/codeql-action/commit/951a133f96aa2114dd747e9e437305335d0bde16"><code>951a133</code></a> Update changelog for v4.37.7</li> <li><a href="https://github.com/github/codeql-action/commit/be7a3dbb8147b82cd6d27e0707105b36aa190fc1"><code>be7a3db</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4087">#4087</a> from github/dependabot/npm_and_yarn/npm-minor-0aa561...</li> <li><a href="https://github.com/github/codeql-action/commit/9310334b11405b305d9444edfa56cd86e2f1e4fe"><code>9310334</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4086">#4086</a> from github/mbg/thread-action-state-to-codeql</li> <li><a href="https://github.com/github/codeql-action/commit/b4d8a54218a8792de9af2f6f32e33af899ca5212"><code>b4d8a54</code></a> Rebuild</li> <li><a href="https://github.com/github/codeql-action/commit/ab5db2519c3344f2fa61c711fa2d6ad135829200"><code>ab5db25</code></a> Bump the npm-minor group across 1 directory with 8 updates</li> <li><a href="https://github.com/github/codeql-action/commit/38055a3c3cf3979323eaf70fc6c73a8690250bde"><code>38055a3</code></a> Drop <code>logger</code> from <code>databaseInitCluster</code> in interface</li> <li><a href="https://github.com/github/codeql-action/commit/1f87aed5e66849f0c43ae147377cc77f2d98ac99"><code>1f87aed</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4085">#4085</a> from github/update-bundle/codeql-bundle-v2.26.3</li> <li><a href="https://github.com/github/codeql-action/commit/dc1b98ad1c2f13ccf9fc33fb82f32fc76f944253"><code>dc1b98a</code></a> Make <code>logger</code> available to <code>getCodeQLForCmd</code></li> <li><a href="https://github.com/github/codeql-action/commit/6f0220ee37121218af472efbde25f06907a4da4f"><code>6f0220e</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4084">#4084</a> from github/navntoft/bump-undici</li> <li>Additional commits viewable in <a href="https://github.com/github/codeql-action/compare/5595ccaf912efad79be6eef63a5619ff05969be3...ff2f1c621b7f889edc0d3c761ac2e6a3f8cdb0dd">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github/codeql-action/upload-sarif&package-manager=github_actions&previous-version=4.37.6&new-version=4.37.7)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2026-08-20 19:32:53 +00:00
dependabot[bot]	1f337c06e4	build(deps-dev): bump uvicorn from 0.52.1 to 0.52.3 in /engine (#7600 ) Bumps [uvicorn](https://github.com/Kludex/uvicorn) from 0.52.1 to 0.52.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Kludex/uvicorn/releases">uvicorn's releases</a>.</em></p> <blockquote> <h2>Version 0.52.3</h2> <h3>Changed</h3> <ul> <li>Update <code>zttp</code> to 0.0.24 and use its combined receive path, improving HTTP/1.1 request parsing performance (<a href="https://redirect.github.com/Kludex/uvicorn/issues/3067">#3067</a>)</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/Kludex/uvicorn/compare/0.52.2...0.52.3">https://github.com/Kludex/uvicorn/compare/0.52.2...0.52.3</a></p> <h2>Version 0.52.2</h2> <h3>Fixed</h3> <ul> <li>Update <code>zttp</code> to 0.0.22, fixing bodyless request receives and improving HTTP/1 request parsing performance (<a href="https://redirect.github.com/Kludex/uvicorn/issues/3063">#3063</a>)</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/Kludex/uvicorn/compare/0.52.1...0.52.2">https://github.com/Kludex/uvicorn/compare/0.52.1...0.52.2</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Kludex/uvicorn/blob/main/docs/release-notes.md">uvicorn's changelog</a>.</em></p> <blockquote> <h2>0.52.3 (August 13, 2026)</h2> <h3>Changed</h3> <ul> <li>Update <code>zttp</code> to 0.0.24 and use its combined receive path, improving HTTP/1.1 request parsing performance (<a href="https://redirect.github.com/Kludex/uvicorn/issues/3067">#3067</a>)</li> </ul> <h2>0.52.2 (August 13, 2026)</h2> <h3>Fixed</h3> <ul> <li>Update <code>zttp</code> to 0.0.22, fixing bodyless request receives and improving HTTP/1 request parsing performance (<a href="https://redirect.github.com/Kludex/uvicorn/issues/3063">#3063</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/Kludex/uvicorn/commit/a68da608147c5f79d962352dce11de8f6e32d972"><code>a68da60</code></a> Version 0.52.3 (<a href="https://redirect.github.com/Kludex/uvicorn/issues/3068">#3068</a>)</li> <li><a href="https://github.com/Kludex/uvicorn/commit/6e3bb4c5c22531c16d341f2da49f2653307f412f"><code>6e3bb4c</code></a> Use zttp 0.0.24 fast receive path (<a href="https://redirect.github.com/Kludex/uvicorn/issues/3067">#3067</a>)</li> <li><a href="https://github.com/Kludex/uvicorn/commit/2a5ff183e02e6dce62f363009c85574bd5a23de2"><code>2a5ff18</code></a> Version 0.52.2 (<a href="https://redirect.github.com/Kludex/uvicorn/issues/3066">#3066</a>)</li> <li><a href="https://github.com/Kludex/uvicorn/commit/1920297df92b9cf5e6befb00327c1e34276db46f"><code>1920297</code></a> Update zttp to 0.0.22 (<a href="https://redirect.github.com/Kludex/uvicorn/issues/3063">#3063</a>)</li> <li><a href="https://github.com/Kludex/uvicorn/commit/5c560dae6a87f6109d958c6154277f1dc727f704"><code>5c560da</code></a> chore(deps): bump pymdown-extensions from 11.0 to 11.0.1 (<a href="https://redirect.github.com/Kludex/uvicorn/issues/3061">#3061</a>)</li> <li>See full diff in <a href="https://github.com/Kludex/uvicorn/compare/0.52.1...0.52.3">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=uvicorn&package-manager=uv&previous-version=0.52.1&new-version=0.52.3)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2026-08-20 19:32:41 +00:00
Vivek Maddheshiya	fb0bffaa31	fix(billing): enforce en-US locale for billing money formatting (#7487 ) (#7498 ) # Description of Changes Fixes #7487 - What was changed: Explicitly specified the `'en-US'` locale in `Intl.NumberFormat` and `toLocaleString` within `formatMinor` and `formatMoneyMajor` in `frontend/editor/src/proprietary/billing/format.ts`. Also added test coverage for `formatMoneyMajor` in `frontend/editor/src/portal/billing/sharedBillingFormat.test.ts`. - Why the change was made: Previously, `formatMinor` used `new Intl.NumberFormat(undefined, ...)`, which inherited the host/browser environment locale. On non-US locales (e.g. German `de-DE`), this produced comma-separated decimals (`$2,24`) instead of dot-separated decimals (`$2.24`), breaking unit tests and leading to inconsistent money formatting. - Any challenges encountered: None. Closes #7487 --- ## Checklist ### General - [x] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [x] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [x] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [x] I have performed a self-review of my own code - [x] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [x] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [x] I have run `task check` to verify linters, typechecks, and tests pass - [x] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-20 19:27:58 +00:00
Ludy	df74c46211	ci: clean up temporary files in GitHub Actions workflows (#7582 ) # Description of Changes This change adds cleanup steps to GitHub Actions workflows that create temporary files or sensitive build resources. Changes include: - Removing temporary backend helper files, logs, and PID files. - Cleaning up database migration temporary directories after failure logs are uploaded. - Removing locally generated deployment files and Storybook archives. - Deleting temporary signing certificates, MSI extraction directories, and Apple signing keychains. - Ensuring cleanup runs even when earlier workflow steps fail. The cleanup reduces temporary data retention on runners and ensures sensitive signing material is removed after builds. No functional application code was changed. --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have run `task check` to verify linters, typechecks, and tests pass - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-20 18:57:03 +00:00
Ludy	4f2b1bb381	Cache Docker dependency downloads in embedded images (#7535 ) # Description of Changes Adds Docker BuildKit syntax and shared Gradle/npm cache mounts to the fat and ultra-lite embedded Dockerfiles. This reduces repeated dependency downloads during rebuilds and speeds up image builds without changing runtime behavior. --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have run `task check` to verify linters, typechecks, and tests pass - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-20 18:56:59 +00:00
Ludy	a24fcb0489	chore(dependabot): refresh dependency update configuration (#7561 ) # Description of Changes - Added `/testing/compose/mcp-client-check` to the existing Docker Compose dependency monitoring configuration so dependencies used by the MCP client check environment are covered by Dependabot. - Added a `tanstack` dependency group matching `@tanstack/` packages, allowing related TanStack updates to be reviewed together. - Added a `typescript` dependency group covering both `typescript` and `@typescript/` packages. - Removed the obsolete `pip` Dependabot configuration for `/testing/cucumber`, as dependency management for this area has moved to the current `uv`-based setup. - Kept the existing Dependabot scheduling, cooldown, grouping, and rebase strategy conventions unchanged where applicable. --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have run `task check` to verify linters, typechecks, and tests pass - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-20 18:33:06 +00:00
Ludy	17938ff5bc	ci: automate Gradle and Docker image updates (#7464 ) ## Summary - Add a scheduled GitHub Actions workflow that checks for the latest stable Gradle release. - Update the Gradle wrapper and pinned Gradle Docker build images automatically. - Open an automated pull request when an update is available. - Update the developer prerequisites to Node.js 22+ and Gradle 9.0+. ## Details The workflow runs every Monday at 03:00 UTC and can also be triggered manually. It: 1. Resolves the latest stable Gradle version. 2. Finds the matching `gradle:<version>-jdk25` Docker image digest. 3. Updates the Gradle wrapper and Dockerfiles. 4. Verifies the resolved wrapper version and checks the resulting diff. 5. Creates or updates an automated dependency pull request. The current wrapper and Docker image changes are included as the initial update generated by this workflow. ## Testing - Verified the generated changes with `git diff --check`. - The workflow validates the wrapper version before opening the automated pull request.	2026-08-20 19:32:54 +01:00
Ludy	73a78ab423	ci: gate backend builds and cache priming (#7405 ) # Description of Changes - Added a dedicated backend path filter for Java and Gradle-related changes. - Gated backend builds on backend-relevant file changes. - Limited Gradle cache priming to project changes. - Made Docker image tests resilient to skipped upstream jobs. - Included the Gradle cache prime job in the final CI status check. - Removed the unnecessary build dependency from the license check. --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have run `task check` to verify linters, typechecks, and tests pass - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-20 19:32:11 +01:00
stirlingbot[bot]	6d549c39dc	Update Frontend 3rd Party Licenses (#7594 ) Auto-generated by stirlingbot[bot] This PR updates the frontend license report based on changes to package.json dependencies. Signed-off-by: stirlingbot[bot] <stirlingbot[bot]@users.noreply.github.com> Co-authored-by: stirlingbot[bot] <195170888+stirlingbot[bot]@users.noreply.github.com>	2026-08-20 16:04:27 +00:00
dependabot[bot]	71af798da4	build(deps): bump the simple-java-mail group across 2 directories with 2 updates (#7585 ) Bumps the simple-java-mail group with 1 update in the / directory: [org.simplejavamail:simple-java-mail](https://github.com/bbottema/simple-java-mail). Bumps the simple-java-mail group with 1 update in the /app/common directory: [org.simplejavamail:simple-java-mail](https://github.com/bbottema/simple-java-mail). Updates `org.simplejavamail:simple-java-mail` from 9.2.0 to 9.3.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/bbottema/simple-java-mail/releases">org.simplejavamail:simple-java-mail's releases</a>.</em></p> <blockquote> <h2>v9.3.1</h2> <p>Simple Java Mail 9.3.1 is a Java 8-compatible build-tool maintenance release.</p> <h2>Changes</h2> <ul> <li>Updated Maven Antrun Plugin from 3.1.0 to 3.2.0 for the JPMS consumer-compilation check.</li> <li>Updated Maven Dependency Plugin from 3.8.1 to 3.11.0 for construction of the JPMS module path.</li> </ul> <p>These changes affect project build tooling only. This release contains no runtime-dependency changes, public API changes, or intended mail-sending behavior changes. Java 8 remains the minimum supported runtime.</p> <p>The maintenance pull requests are <a href="https://redirect.github.com/bbottema/simple-java-mail/pull/700">#700</a> and <a href="https://redirect.github.com/bbottema/simple-java-mail/pull/701">#701</a>.</p> <h2>v9.3.0</h2> <p>Simple Java Mail 9.3.0 exposes <code>batch-module</code> as a supported standalone Jakarta Mail orchestration API.</p> <ul> <li><a href="https://redirect.github.com/bbottema/simple-java-mail/issues/698">#698</a> adds <code>BatchTransportExecutor<K></code> for applications that create their own <code>Session</code> and <code>MimeMessage</code> objects without adopting <code>EmailBuilder</code> or <code>Mailer</code>. The main <code>simple-java-mail</code> facade is not required.</li> <li>Register Sessions by cluster key, then run cluster-selected or exact-Session callbacks synchronously or submit them as <code>CompletableFuture</code> work. Each callback receives the actually selected <code>Session</code> and connected <code>Transport</code>.</li> <li>The facade keeps raw leases private, releases connections after successful callbacks, invalidates them after escaping failures, resolves OAuth2 credentials from the selected Session, and provides deterministic graceful or forced shutdown. Its default executor is module-owned; an injected executor remains caller-owned.</li> <li>The existing pooled <code>Mailer</code> path and the standalone facade now share one transport engine. <code>smtp-connection-pool</code> remains the only physical pool owner; do not stack batch/direct orchestration over the Jakarta <code>smtppool</code> provider.</li> <li>The supporting chain is updated to <code>smtp-connection-pool 4.0.1</code>, <code>clustered-object-pool 4.0.3</code>, and <code>generic-object-pool 2.4.2</code>. The published JPMS names are <code>org.simplejavamail.batch</code>, <code>org.simplejavamail.smtpconnectionpool</code>, <code>org.bbottema.clusteredobjectpool</code>, and <code>org.bbottema.genericobjectpool</code>.</li> </ul> <p>See the <a href="https://www.simplejavamail.org/smtp-connection-pooling.html">SMTP connection pooling and batch orchestration guide</a> for the comparison matrix, ownership rules, and complete examples.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/bbottema/simple-java-mail/blob/master/RELEASE.txt">org.simplejavamail:simple-java-mail's changelog</a>.</em></p> <blockquote> <p><a href="https://www.simplejavamail.org">https://www.simplejavamail.org</a></p> <!-- raw HTML omitted --> <p>v9.3.0 - v9.3.2</p> <ul> <li><strong>v9.3.2:</strong> <a href="https://redirect.github.com/bbottema/simple-java-mail/issues/702">#702</a>: clarified the single-address contract of RecipientBuilder by renaming its misleading implementation parameter and validation label; use RecipientsBuilder for comma- or semicolon-delimited address lists.</li> <li><strong>v9.3.1:</strong> Updated Maven Antrun Plugin from 3.1.0 to 3.2.0 (<a href="https://redirect.github.com/bbottema/simple-java-mail/issues/700">#700</a>) and Maven Dependency Plugin from 3.8.1 to 3.11.0 (<a href="https://redirect.github.com/bbottema/simple-java-mail/issues/701">#701</a>), retaining Java 8 compatibility.</li> <li><strong>v9.3.0:</strong> <a href="https://redirect.github.com/bbottema/simple-java-mail/issues/698">#698</a>: exposed batch-module as a supported standalone Jakarta Mail orchestration API with clustered and exact-Session callbacks, asynchronous submission, automatic lease release/invalidation, and deterministic graceful or forced shutdown.</li> <li><strong>v9.3.0:</strong> Updated smtp-connection-pool from 3.1.0 to 4.0.1 and migrated the existing Mailer integration to its explicit SmtpTransportLease contract. The complete generic, clustered, SMTP, and batch dependency chain now publishes stable JPMS automatic module names.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/bbottema/simple-java-mail/commit/e44c4c983e48ec9372ff745ccb9ab01d731867d0"><code>e44c4c9</code></a> released 9.3.1 [skip ci]</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/461e5f7c3b97d4882b21bca7ecb4843530184f32"><code>461e5f7</code></a> docs(release): prepare 9.3.1 release notes</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/68728f3457f7b0e85cf66e758f41985b86c4a125"><code>68728f3</code></a> build(deps-dev): bump org.apache.maven.plugins:maven-dependency-plugin (<a href="https://redirect.github.com/bbottema/simple-java-mail/issues/701">#701</a>)</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/d491c334bea647a99538984d917cd6ffdcb3cbce"><code>d491c33</code></a> build(deps-dev): bump org.apache.maven.plugins:maven-antrun-plugin (<a href="https://redirect.github.com/bbottema/simple-java-mail/issues/700">#700</a>)</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/b3111e232a23f9187c2b0c6b98a0bb1a895d9309"><code>b3111e2</code></a> docs(website): publish pooling guidance update [skip ci]</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/cb3a9a133b91372d112c1b6a07c92e721f1a6f9e"><code>cb3a9a1</code></a> docs(website): publish pooling guide follow-up [skip ci]</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/29f25e83c654d5dbadd4da321ce9511a4eceeeef"><code>29f25e8</code></a> released 9.3.0 [skip ci]</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/b9c0cb8b58f4477e92fdd7ea395583863f875310"><code>b9c0cb8</code></a> feat(batch): expose standalone transport orchestration</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/92549b27f44a0042ca908d22c25db58ccc1e1630"><code>92549b2</code></a> merge(release): reconcile master with develop [skip ci]</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/b499d76ec28e0566b2000ec6418473da66e1398a"><code>b499d76</code></a> docs(readme): rebuild developer landing page [skip ci]</li> <li>Additional commits viewable in <a href="https://github.com/bbottema/simple-java-mail/compare/9.2.0...9.3.1">compare view</a></li> </ul> </details> <br /> Updates `org.simplejavamail:outlook-module` from 9.2.0 to 9.3.1 Updates `org.simplejavamail:simple-java-mail` from 9.2.0 to 9.3.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/bbottema/simple-java-mail/releases">org.simplejavamail:simple-java-mail's releases</a>.</em></p> <blockquote> <h2>v9.3.1</h2> <p>Simple Java Mail 9.3.1 is a Java 8-compatible build-tool maintenance release.</p> <h2>Changes</h2> <ul> <li>Updated Maven Antrun Plugin from 3.1.0 to 3.2.0 for the JPMS consumer-compilation check.</li> <li>Updated Maven Dependency Plugin from 3.8.1 to 3.11.0 for construction of the JPMS module path.</li> </ul> <p>These changes affect project build tooling only. This release contains no runtime-dependency changes, public API changes, or intended mail-sending behavior changes. Java 8 remains the minimum supported runtime.</p> <p>The maintenance pull requests are <a href="https://redirect.github.com/bbottema/simple-java-mail/pull/700">#700</a> and <a href="https://redirect.github.com/bbottema/simple-java-mail/pull/701">#701</a>.</p> <h2>v9.3.0</h2> <p>Simple Java Mail 9.3.0 exposes <code>batch-module</code> as a supported standalone Jakarta Mail orchestration API.</p> <ul> <li><a href="https://redirect.github.com/bbottema/simple-java-mail/issues/698">#698</a> adds <code>BatchTransportExecutor<K></code> for applications that create their own <code>Session</code> and <code>MimeMessage</code> objects without adopting <code>EmailBuilder</code> or <code>Mailer</code>. The main <code>simple-java-mail</code> facade is not required.</li> <li>Register Sessions by cluster key, then run cluster-selected or exact-Session callbacks synchronously or submit them as <code>CompletableFuture</code> work. Each callback receives the actually selected <code>Session</code> and connected <code>Transport</code>.</li> <li>The facade keeps raw leases private, releases connections after successful callbacks, invalidates them after escaping failures, resolves OAuth2 credentials from the selected Session, and provides deterministic graceful or forced shutdown. Its default executor is module-owned; an injected executor remains caller-owned.</li> <li>The existing pooled <code>Mailer</code> path and the standalone facade now share one transport engine. <code>smtp-connection-pool</code> remains the only physical pool owner; do not stack batch/direct orchestration over the Jakarta <code>smtppool</code> provider.</li> <li>The supporting chain is updated to <code>smtp-connection-pool 4.0.1</code>, <code>clustered-object-pool 4.0.3</code>, and <code>generic-object-pool 2.4.2</code>. The published JPMS names are <code>org.simplejavamail.batch</code>, <code>org.simplejavamail.smtpconnectionpool</code>, <code>org.bbottema.clusteredobjectpool</code>, and <code>org.bbottema.genericobjectpool</code>.</li> </ul> <p>See the <a href="https://www.simplejavamail.org/smtp-connection-pooling.html">SMTP connection pooling and batch orchestration guide</a> for the comparison matrix, ownership rules, and complete examples.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/bbottema/simple-java-mail/blob/master/RELEASE.txt">org.simplejavamail:simple-java-mail's changelog</a>.</em></p> <blockquote> <p><a href="https://www.simplejavamail.org">https://www.simplejavamail.org</a></p> <!-- raw HTML omitted --> <p>v9.3.0 - v9.3.2</p> <ul> <li><strong>v9.3.2:</strong> <a href="https://redirect.github.com/bbottema/simple-java-mail/issues/702">#702</a>: clarified the single-address contract of RecipientBuilder by renaming its misleading implementation parameter and validation label; use RecipientsBuilder for comma- or semicolon-delimited address lists.</li> <li><strong>v9.3.1:</strong> Updated Maven Antrun Plugin from 3.1.0 to 3.2.0 (<a href="https://redirect.github.com/bbottema/simple-java-mail/issues/700">#700</a>) and Maven Dependency Plugin from 3.8.1 to 3.11.0 (<a href="https://redirect.github.com/bbottema/simple-java-mail/issues/701">#701</a>), retaining Java 8 compatibility.</li> <li><strong>v9.3.0:</strong> <a href="https://redirect.github.com/bbottema/simple-java-mail/issues/698">#698</a>: exposed batch-module as a supported standalone Jakarta Mail orchestration API with clustered and exact-Session callbacks, asynchronous submission, automatic lease release/invalidation, and deterministic graceful or forced shutdown.</li> <li><strong>v9.3.0:</strong> Updated smtp-connection-pool from 3.1.0 to 4.0.1 and migrated the existing Mailer integration to its explicit SmtpTransportLease contract. The complete generic, clustered, SMTP, and batch dependency chain now publishes stable JPMS automatic module names.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/bbottema/simple-java-mail/commit/e44c4c983e48ec9372ff745ccb9ab01d731867d0"><code>e44c4c9</code></a> released 9.3.1 [skip ci]</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/461e5f7c3b97d4882b21bca7ecb4843530184f32"><code>461e5f7</code></a> docs(release): prepare 9.3.1 release notes</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/68728f3457f7b0e85cf66e758f41985b86c4a125"><code>68728f3</code></a> build(deps-dev): bump org.apache.maven.plugins:maven-dependency-plugin (<a href="https://redirect.github.com/bbottema/simple-java-mail/issues/701">#701</a>)</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/d491c334bea647a99538984d917cd6ffdcb3cbce"><code>d491c33</code></a> build(deps-dev): bump org.apache.maven.plugins:maven-antrun-plugin (<a href="https://redirect.github.com/bbottema/simple-java-mail/issues/700">#700</a>)</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/b3111e232a23f9187c2b0c6b98a0bb1a895d9309"><code>b3111e2</code></a> docs(website): publish pooling guidance update [skip ci]</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/cb3a9a133b91372d112c1b6a07c92e721f1a6f9e"><code>cb3a9a1</code></a> docs(website): publish pooling guide follow-up [skip ci]</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/29f25e83c654d5dbadd4da321ce9511a4eceeeef"><code>29f25e8</code></a> released 9.3.0 [skip ci]</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/b9c0cb8b58f4477e92fdd7ea395583863f875310"><code>b9c0cb8</code></a> feat(batch): expose standalone transport orchestration</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/92549b27f44a0042ca908d22c25db58ccc1e1630"><code>92549b2</code></a> merge(release): reconcile master with develop [skip ci]</li> <li><a href="https://github.com/bbottema/simple-java-mail/commit/b499d76ec28e0566b2000ec6418473da66e1398a"><code>b499d76</code></a> docs(readme): rebuild developer landing page [skip ci]</li> <li>Additional commits viewable in <a href="https://github.com/bbottema/simple-java-mail/compare/9.2.0...9.3.1">compare view</a></li> </ul> </details> <br /> Updates `org.simplejavamail:outlook-module` from 9.2.0 to 9.3.1 Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2026-08-20 15:00:25 +00:00
dependabot[bot]	d9a5c9ac7e	build(deps): bump the embedpdf group across 1 directory with 23 updates (#7469 ) Bumps the embedpdf group with 21 updates in the /frontend directory: \| Package \| From \| To \| \| --- \| --- \| --- \| \| [@embedpdf/core](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/core/main) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/models](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/models) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-annotation](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-annotation) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-attachment](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-attachment) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-bookmark](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-bookmark) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-document-manager](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-document-manager) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-export](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-download) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-history](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-history) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-interaction-manager](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-interaction-manager) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-pan](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-pan) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-print](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-print) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-redaction](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-redaction) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-render](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-render) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-rotate](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-rotate) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-scroll](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-scroll) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-search](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-search) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-spread](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-spread) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-thumbnail](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-thumbnail) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-tiling](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-tiling) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-viewport](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-viewport) \| `2.14.4` \| `2.15.0` \| \| [@embedpdf/plugin-zoom](https://github.com/embedpdf/embed-pdf-viewer/tree/HEAD/packages/plugin-zoom) \| `2.14.4` \| `2.15.0` \| Updates `@embedpdf/core` from 2.14.4 to 2.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/releases">@embedpdf/core's releases</a>.</em></p> <blockquote> <h2>Release v2.15.0</h2> <h2><code>@embedpdf/plugin-selection</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/685">#685</a> by <a href="https://github.com/simonmysun"><code>@simonmysun</code></a> – Add <code>setSelection(range, documentId?)</code> to the selection capability and document scope for programmatically applying or restoring a text selection.</p> <p>It accepts the same <code>SelectionRangeX</code> (<code>{ start, end }</code> glyph pointers) shape emitted by <code>onSelectionChange</code>, so a saved selection can be passed straight back in to restore it; passing <code>null</code> clears the selection. Page geometry is loaded on demand, so the returned task resolves only once the highlight rects are computed. The range is normalized (start/end may be given in any order), invalid input (malformed range, non-integer/negative indices, out-of-bounds pages) is rejected, glyph indices are clamped to the available page geometry, and previously highlighted pages are repainted so switching to a disjoint selection no longer leaves stale highlights behind.</p> </li> </ul> <h2><code>@embedpdf/core</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/703">#703</a> by <a href="https://github.com/berkayozdin"><code>@berkayozdin</code></a> – Make the precompiled Svelte output work on every Svelte 5 runtime</p> <p>Svelte 5.56 changed the <code>exclude</code> argument of the private <code>rest_props</code> runtime helper from an array (<code>exclude.includes(key)</code>) to a <code>Set</code> (<code>exclude.has(key)</code>). The <code>/svelte</code> entry points ship precompiled component code, so output built against one side of that change throws on the other: the currently published packages fail with <code>TypeError: exclude.has is not a function</code> on Svelte >= 5.56, which aborts the render of every EmbedPDF Svelte component.</p> <p>The Svelte build now routes those calls through a wrapper that hands the runtime an <code>exclude</code> value satisfying both contracts, so one published build stays valid across the whole <code>svelte: ">=5 <6"</code> peer range.</p> </li> </ul> <h2><code>@embedpdf/engines</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/models</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/pdfium</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-annotation</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-attachment</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-bookmark</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-capture</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-commands</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-document-manager</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-export</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-form</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/embedpdf/embed-pdf-viewer/commits/v2.15.0/packages/core/main">compare view</a></li> </ul> </details> <br /> Updates `@embedpdf/engines` from 2.14.4 to 2.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/releases">@embedpdf/engines's releases</a>.</em></p> <blockquote> <h2>Release v2.15.0</h2> <h2><code>@embedpdf/plugin-selection</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/685">#685</a> by <a href="https://github.com/simonmysun"><code>@simonmysun</code></a> – Add <code>setSelection(range, documentId?)</code> to the selection capability and document scope for programmatically applying or restoring a text selection.</p> <p>It accepts the same <code>SelectionRangeX</code> (<code>{ start, end }</code> glyph pointers) shape emitted by <code>onSelectionChange</code>, so a saved selection can be passed straight back in to restore it; passing <code>null</code> clears the selection. Page geometry is loaded on demand, so the returned task resolves only once the highlight rects are computed. The range is normalized (start/end may be given in any order), invalid input (malformed range, non-integer/negative indices, out-of-bounds pages) is rejected, glyph indices are clamped to the available page geometry, and previously highlighted pages are repainted so switching to a disjoint selection no longer leaves stale highlights behind.</p> </li> </ul> <h2><code>@embedpdf/core</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/703">#703</a> by <a href="https://github.com/berkayozdin"><code>@berkayozdin</code></a> – Make the precompiled Svelte output work on every Svelte 5 runtime</p> <p>Svelte 5.56 changed the <code>exclude</code> argument of the private <code>rest_props</code> runtime helper from an array (<code>exclude.includes(key)</code>) to a <code>Set</code> (<code>exclude.has(key)</code>). The <code>/svelte</code> entry points ship precompiled component code, so output built against one side of that change throws on the other: the currently published packages fail with <code>TypeError: exclude.has is not a function</code> on Svelte >= 5.56, which aborts the render of every EmbedPDF Svelte component.</p> <p>The Svelte build now routes those calls through a wrapper that hands the runtime an <code>exclude</code> value satisfying both contracts, so one published build stays valid across the whole <code>svelte: ">=5 <6"</code> peer range.</p> </li> </ul> <h2><code>@embedpdf/engines</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/models</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/pdfium</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-annotation</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-attachment</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-bookmark</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-capture</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-commands</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-document-manager</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-export</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-form</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/blob/v2.15.0/packages/engines/CHANGELOG.md">@embedpdf/engines's changelog</a>.</em></p> <blockquote> <h2>2.15.0</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/embedpdf/embed-pdf-viewer/commit/a8faf04b15291c895118b819d7395c3bca8a4959"><code>a8faf04</code></a> chore: version packages</li> <li>See full diff in <a href="https://github.com/embedpdf/embed-pdf-viewer/commits/v2.15.0/packages/engines">compare view</a></li> </ul> </details> <br /> Updates `@embedpdf/models` from 2.14.4 to 2.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/releases">@embedpdf/models's releases</a>.</em></p> <blockquote> <h2>Release v2.15.0</h2> <h2><code>@embedpdf/plugin-selection</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/685">#685</a> by <a href="https://github.com/simonmysun"><code>@simonmysun</code></a> – Add <code>setSelection(range, documentId?)</code> to the selection capability and document scope for programmatically applying or restoring a text selection.</p> <p>It accepts the same <code>SelectionRangeX</code> (<code>{ start, end }</code> glyph pointers) shape emitted by <code>onSelectionChange</code>, so a saved selection can be passed straight back in to restore it; passing <code>null</code> clears the selection. Page geometry is loaded on demand, so the returned task resolves only once the highlight rects are computed. The range is normalized (start/end may be given in any order), invalid input (malformed range, non-integer/negative indices, out-of-bounds pages) is rejected, glyph indices are clamped to the available page geometry, and previously highlighted pages are repainted so switching to a disjoint selection no longer leaves stale highlights behind.</p> </li> </ul> <h2><code>@embedpdf/core</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/703">#703</a> by <a href="https://github.com/berkayozdin"><code>@berkayozdin</code></a> – Make the precompiled Svelte output work on every Svelte 5 runtime</p> <p>Svelte 5.56 changed the <code>exclude</code> argument of the private <code>rest_props</code> runtime helper from an array (<code>exclude.includes(key)</code>) to a <code>Set</code> (<code>exclude.has(key)</code>). The <code>/svelte</code> entry points ship precompiled component code, so output built against one side of that change throws on the other: the currently published packages fail with <code>TypeError: exclude.has is not a function</code> on Svelte >= 5.56, which aborts the render of every EmbedPDF Svelte component.</p> <p>The Svelte build now routes those calls through a wrapper that hands the runtime an <code>exclude</code> value satisfying both contracts, so one published build stays valid across the whole <code>svelte: ">=5 <6"</code> peer range.</p> </li> </ul> <h2><code>@embedpdf/engines</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/models</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/pdfium</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-annotation</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-attachment</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-bookmark</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-capture</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-commands</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-document-manager</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-export</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-form</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/blob/v2.15.0/packages/models/CHANGELOG.md">@embedpdf/models's changelog</a>.</em></p> <blockquote> <h2>2.15.0</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/embedpdf/embed-pdf-viewer/commit/a8faf04b15291c895118b819d7395c3bca8a4959"><code>a8faf04</code></a> chore: version packages</li> <li>See full diff in <a href="https://github.com/embedpdf/embed-pdf-viewer/commits/v2.15.0/packages/models">compare view</a></li> </ul> </details> <br /> Updates `@embedpdf/plugin-annotation` from 2.14.4 to 2.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/releases">@embedpdf/plugin-annotation's releases</a>.</em></p> <blockquote> <h2>Release v2.15.0</h2> <h2><code>@embedpdf/plugin-selection</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/685">#685</a> by <a href="https://github.com/simonmysun"><code>@simonmysun</code></a> – Add <code>setSelection(range, documentId?)</code> to the selection capability and document scope for programmatically applying or restoring a text selection.</p> <p>It accepts the same <code>SelectionRangeX</code> (<code>{ start, end }</code> glyph pointers) shape emitted by <code>onSelectionChange</code>, so a saved selection can be passed straight back in to restore it; passing <code>null</code> clears the selection. Page geometry is loaded on demand, so the returned task resolves only once the highlight rects are computed. The range is normalized (start/end may be given in any order), invalid input (malformed range, non-integer/negative indices, out-of-bounds pages) is rejected, glyph indices are clamped to the available page geometry, and previously highlighted pages are repainted so switching to a disjoint selection no longer leaves stale highlights behind.</p> </li> </ul> <h2><code>@embedpdf/core</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/703">#703</a> by <a href="https://github.com/berkayozdin"><code>@berkayozdin</code></a> – Make the precompiled Svelte output work on every Svelte 5 runtime</p> <p>Svelte 5.56 changed the <code>exclude</code> argument of the private <code>rest_props</code> runtime helper from an array (<code>exclude.includes(key)</code>) to a <code>Set</code> (<code>exclude.has(key)</code>). The <code>/svelte</code> entry points ship precompiled component code, so output built against one side of that change throws on the other: the currently published packages fail with <code>TypeError: exclude.has is not a function</code> on Svelte >= 5.56, which aborts the render of every EmbedPDF Svelte component.</p> <p>The Svelte build now routes those calls through a wrapper that hands the runtime an <code>exclude</code> value satisfying both contracts, so one published build stays valid across the whole <code>svelte: ">=5 <6"</code> peer range.</p> </li> </ul> <h2><code>@embedpdf/engines</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/models</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/pdfium</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-annotation</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-attachment</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-bookmark</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-capture</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-commands</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-document-manager</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-export</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-form</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/blob/v2.15.0/packages/plugin-annotation/CHANGELOG.md">@embedpdf/plugin-annotation's changelog</a>.</em></p> <blockquote> <h2>2.15.0</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/embedpdf/embed-pdf-viewer/commit/a8faf04b15291c895118b819d7395c3bca8a4959"><code>a8faf04</code></a> chore: version packages</li> <li>See full diff in <a href="https://github.com/embedpdf/embed-pdf-viewer/commits/v2.15.0/packages/plugin-annotation">compare view</a></li> </ul> </details> <br /> Updates `@embedpdf/plugin-attachment` from 2.14.4 to 2.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/releases">@embedpdf/plugin-attachment's releases</a>.</em></p> <blockquote> <h2>Release v2.15.0</h2> <h2><code>@embedpdf/plugin-selection</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/685">#685</a> by <a href="https://github.com/simonmysun"><code>@simonmysun</code></a> – Add <code>setSelection(range, documentId?)</code> to the selection capability and document scope for programmatically applying or restoring a text selection.</p> <p>It accepts the same <code>SelectionRangeX</code> (<code>{ start, end }</code> glyph pointers) shape emitted by <code>onSelectionChange</code>, so a saved selection can be passed straight back in to restore it; passing <code>null</code> clears the selection. Page geometry is loaded on demand, so the returned task resolves only once the highlight rects are computed. The range is normalized (start/end may be given in any order), invalid input (malformed range, non-integer/negative indices, out-of-bounds pages) is rejected, glyph indices are clamped to the available page geometry, and previously highlighted pages are repainted so switching to a disjoint selection no longer leaves stale highlights behind.</p> </li> </ul> <h2><code>@embedpdf/core</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/703">#703</a> by <a href="https://github.com/berkayozdin"><code>@berkayozdin</code></a> – Make the precompiled Svelte output work on every Svelte 5 runtime</p> <p>Svelte 5.56 changed the <code>exclude</code> argument of the private <code>rest_props</code> runtime helper from an array (<code>exclude.includes(key)</code>) to a <code>Set</code> (<code>exclude.has(key)</code>). The <code>/svelte</code> entry points ship precompiled component code, so output built against one side of that change throws on the other: the currently published packages fail with <code>TypeError: exclude.has is not a function</code> on Svelte >= 5.56, which aborts the render of every EmbedPDF Svelte component.</p> <p>The Svelte build now routes those calls through a wrapper that hands the runtime an <code>exclude</code> value satisfying both contracts, so one published build stays valid across the whole <code>svelte: ">=5 <6"</code> peer range.</p> </li> </ul> <h2><code>@embedpdf/engines</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/models</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/pdfium</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-annotation</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-attachment</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-bookmark</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-capture</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-commands</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-document-manager</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-export</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-form</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/blob/v2.15.0/packages/plugin-attachment/CHANGELOG.md">@embedpdf/plugin-attachment's changelog</a>.</em></p> <blockquote> <h2>2.15.0</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/embedpdf/embed-pdf-viewer/commit/a8faf04b15291c895118b819d7395c3bca8a4959"><code>a8faf04</code></a> chore: version packages</li> <li>See full diff in <a href="https://github.com/embedpdf/embed-pdf-viewer/commits/v2.15.0/packages/plugin-attachment">compare view</a></li> </ul> </details> <br /> Updates `@embedpdf/plugin-bookmark` from 2.14.4 to 2.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/releases">@embedpdf/plugin-bookmark's releases</a>.</em></p> <blockquote> <h2>Release v2.15.0</h2> <h2><code>@embedpdf/plugin-selection</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/685">#685</a> by <a href="https://github.com/simonmysun"><code>@simonmysun</code></a> – Add <code>setSelection(range, documentId?)</code> to the selection capability and document scope for programmatically applying or restoring a text selection.</p> <p>It accepts the same <code>SelectionRangeX</code> (<code>{ start, end }</code> glyph pointers) shape emitted by <code>onSelectionChange</code>, so a saved selection can be passed straight back in to restore it; passing <code>null</code> clears the selection. Page geometry is loaded on demand, so the returned task resolves only once the highlight rects are computed. The range is normalized (start/end may be given in any order), invalid input (malformed range, non-integer/negative indices, out-of-bounds pages) is rejected, glyph indices are clamped to the available page geometry, and previously highlighted pages are repainted so switching to a disjoint selection no longer leaves stale highlights behind.</p> </li> </ul> <h2><code>@embedpdf/core</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/703">#703</a> by <a href="https://github.com/berkayozdin"><code>@berkayozdin</code></a> – Make the precompiled Svelte output work on every Svelte 5 runtime</p> <p>Svelte 5.56 changed the <code>exclude</code> argument of the private <code>rest_props</code> runtime helper from an array (<code>exclude.includes(key)</code>) to a <code>Set</code> (<code>exclude.has(key)</code>). The <code>/svelte</code> entry points ship precompiled component code, so output built against one side of that change throws on the other: the currently published packages fail with <code>TypeError: exclude.has is not a function</code> on Svelte >= 5.56, which aborts the render of every EmbedPDF Svelte component.</p> <p>The Svelte build now routes those calls through a wrapper that hands the runtime an <code>exclude</code> value satisfying both contracts, so one published build stays valid across the whole <code>svelte: ">=5 <6"</code> peer range.</p> </li> </ul> <h2><code>@embedpdf/engines</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/models</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/pdfium</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-annotation</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-attachment</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-bookmark</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-capture</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-commands</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-document-manager</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-export</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-form</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/blob/v2.15.0/packages/plugin-bookmark/CHANGELOG.md">@embedpdf/plugin-bookmark's changelog</a>.</em></p> <blockquote> <h2>2.15.0</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/embedpdf/embed-pdf-viewer/commit/a8faf04b15291c895118b819d7395c3bca8a4959"><code>a8faf04</code></a> chore: version packages</li> <li>See full diff in <a href="https://github.com/embedpdf/embed-pdf-viewer/commits/v2.15.0/packages/plugin-bookmark">compare view</a></li> </ul> </details> <br /> Updates `@embedpdf/plugin-document-manager` from 2.14.4 to 2.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/releases">@embedpdf/plugin-document-manager's releases</a>.</em></p> <blockquote> <h2>Release v2.15.0</h2> <h2><code>@embedpdf/plugin-selection</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/685">#685</a> by <a href="https://github.com/simonmysun"><code>@simonmysun</code></a> – Add <code>setSelection(range, documentId?)</code> to the selection capability and document scope for programmatically applying or restoring a text selection.</p> <p>It accepts the same <code>SelectionRangeX</code> (<code>{ start, end }</code> glyph pointers) shape emitted by <code>onSelectionChange</code>, so a saved selection can be passed straight back in to restore it; passing <code>null</code> clears the selection. Page geometry is loaded on demand, so the returned task resolves only once the highlight rects are computed. The range is normalized (start/end may be given in any order), invalid input (malformed range, non-integer/negative indices, out-of-bounds pages) is rejected, glyph indices are clamped to the available page geometry, and previously highlighted pages are repainted so switching to a disjoint selection no longer leaves stale highlights behind.</p> </li> </ul> <h2><code>@embedpdf/core</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/703">#703</a> by <a href="https://github.com/berkayozdin"><code>@berkayozdin</code></a> – Make the precompiled Svelte output work on every Svelte 5 runtime</p> <p>Svelte 5.56 changed the <code>exclude</code> argument of the private <code>rest_props</code> runtime helper from an array (<code>exclude.includes(key)</code>) to a <code>Set</code> (<code>exclude.has(key)</code>). The <code>/svelte</code> entry points ship precompiled component code, so output built against one side of that change throws on the other: the currently published packages fail with <code>TypeError: exclude.has is not a function</code> on Svelte >= 5.56, which aborts the render of every EmbedPDF Svelte component.</p> <p>The Svelte build now routes those calls through a wrapper that hands the runtime an <code>exclude</code> value satisfying both contracts, so one published build stays valid across the whole <code>svelte: ">=5 <6"</code> peer range.</p> </li> </ul> <h2><code>@embedpdf/engines</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/models</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/pdfium</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-annotation</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-attachment</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-bookmark</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-capture</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-commands</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-document-manager</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-export</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-form</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/blob/v2.15.0/packages/plugin-document-manager/CHANGELOG.md">@embedpdf/plugin-document-manager's changelog</a>.</em></p> <blockquote> <h2>2.15.0</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/embedpdf/embed-pdf-viewer/commit/a8faf04b15291c895118b819d7395c3bca8a4959"><code>a8faf04</code></a> chore: version packages</li> <li>See full diff in <a href="https://github.com/embedpdf/embed-pdf-viewer/commits/v2.15.0/packages/plugin-document-manager">compare view</a></li> </ul> </details> <br /> Updates `@embedpdf/plugin-export` from 2.14.4 to 2.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/releases">@embedpdf/plugin-export's releases</a>.</em></p> <blockquote> <h2>Release v2.15.0</h2> <h2><code>@embedpdf/plugin-selection</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/685">#685</a> by <a href="https://github.com/simonmysun"><code>@simonmysun</code></a> – Add <code>setSelection(range, documentId?)</code> to the selection capability and document scope for programmatically applying or restoring a text selection.</p> <p>It accepts the same <code>SelectionRangeX</code> (<code>{ start, end }</code> glyph pointers) shape emitted by <code>onSelectionChange</code>, so a saved selection can be passed straight back in to restore it; passing <code>null</code> clears the selection. Page geometry is loaded on demand, so the returned task resolves only once the highlight rects are computed. The range is normalized (start/end may be given in any order), invalid input (malformed range, non-integer/negative indices, out-of-bounds pages) is rejected, glyph indices are clamped to the available page geometry, and previously highlighted pages are repainted so switching to a disjoint selection no longer leaves stale highlights behind.</p> </li> </ul> <h2><code>@embedpdf/core</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/703">#703</a> by <a href="https://github.com/berkayozdin"><code>@berkayozdin</code></a> – Make the precompiled Svelte output work on every Svelte 5 runtime</p> <p>Svelte 5.56 changed the <code>exclude</code> argument of the private <code>rest_props</code> runtime helper from an array (<code>exclude.includes(key)</code>) to a <code>Set</code> (<code>exclude.has(key)</code>). The <code>/svelte</code> entry points ship precompiled component code, so output built against one side of that change throws on the other: the currently published packages fail with <code>TypeError: exclude.has is not a function</code> on Svelte >= 5.56, which aborts the render of every EmbedPDF Svelte component.</p> <p>The Svelte build now routes those calls through a wrapper that hands the runtime an <code>exclude</code> value satisfying both contracts, so one published build stays valid across the whole <code>svelte: ">=5 <6"</code> peer range.</p> </li> </ul> <h2><code>@embedpdf/engines</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/models</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/pdfium</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-annotation</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-attachment</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-bookmark</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-capture</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-commands</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-document-manager</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-export</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-form</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/embedpdf/embed-pdf-viewer/commits/v2.15.0/packages/plugin-download">compare view</a></li> </ul> </details> <br /> Updates `@embedpdf/plugin-history` from 2.14.4 to 2.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/releases">@embedpdf/plugin-history's releases</a>.</em></p> <blockquote> <h2>Release v2.15.0</h2> <h2><code>@embedpdf/plugin-selection</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/685">#685</a> by <a href="https://github.com/simonmysun"><code>@simonmysun</code></a> – Add <code>setSelection(range, documentId?)</code> to the selection capability and document scope for programmatically applying or restoring a text selection.</p> <p>It accepts the same <code>SelectionRangeX</code> (<code>{ start, end }</code> glyph pointers) shape emitted by <code>onSelectionChange</code>, so a saved selection can be passed straight back in to restore it; passing <code>null</code> clears the selection. Page geometry is loaded on demand, so the returned task resolves only once the highlight rects are computed. The range is normalized (start/end may be given in any order), invalid input (malformed range, non-integer/negative indices, out-of-bounds pages) is rejected, glyph indices are clamped to the available page geometry, and previously highlighted pages are repainted so switching to a disjoint selection no longer leaves stale highlights behind.</p> </li> </ul> <h2><code>@embedpdf/core</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/703">#703</a> by <a href="https://github.com/berkayozdin"><code>@berkayozdin</code></a> – Make the precompiled Svelte output work on every Svelte 5 runtime</p> <p>Svelte 5.56 changed the <code>exclude</code> argument of the private <code>rest_props</code> runtime helper from an array (<code>exclude.includes(key)</code>) to a <code>Set</code> (<code>exclude.has(key)</code>). The <code>/svelte</code> entry points ship precompiled component code, so output built against one side of that change throws on the other: the currently published packages fail with <code>TypeError: exclude.has is not a function</code> on Svelte >= 5.56, which aborts the render of every EmbedPDF Svelte component.</p> <p>The Svelte build now routes those calls through a wrapper that hands the runtime an <code>exclude</code> value satisfying both contracts, so one published build stays valid across the whole <code>svelte: ">=5 <6"</code> peer range.</p> </li> </ul> <h2><code>@embedpdf/engines</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/models</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/pdfium</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-annotation</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-attachment</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-bookmark</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-capture</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-commands</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-document-manager</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-export</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-form</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/blob/v2.15.0/packages/plugin-history/CHANGELOG.md">@embedpdf/plugin-history's changelog</a>.</em></p> <blockquote> <h2>2.15.0</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/embedpdf/embed-pdf-viewer/commit/a8faf04b15291c895118b819d7395c3bca8a4959"><code>a8faf04</code></a> chore: version packages</li> <li>See full diff in <a href="https://github.com/embedpdf/embed-pdf-viewer/commits/v2.15.0/packages/plugin-history">compare view</a></li> </ul> </details> <br /> Updates `@embedpdf/plugin-interaction-manager` from 2.14.4 to 2.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/releases">@embedpdf/plugin-interaction-manager's releases</a>.</em></p> <blockquote> <h2>Release v2.15.0</h2> <h2><code>@embedpdf/plugin-selection</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/685">#685</a> by <a href="https://github.com/simonmysun"><code>@simonmysun</code></a> – Add <code>setSelection(range, documentId?)</code> to the selection capability and document scope for programmatically applying or restoring a text selection.</p> <p>It accepts the same <code>SelectionRangeX</code> (<code>{ start, end }</code> glyph pointers) shape emitted by <code>onSelectionChange</code>, so a saved selection can be passed straight back in to restore it; passing <code>null</code> clears the selection. Page geometry is loaded on demand, so the returned task resolves only once the highlight rects are computed. The range is normalized (start/end may be given in any order), invalid input (malformed range, non-integer/negative indices, out-of-bounds pages) is rejected, glyph indices are clamped to the available page geometry, and previously highlighted pages are repainted so switching to a disjoint selection no longer leaves stale highlights behind.</p> </li> </ul> <h2><code>@embedpdf/core</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/703">#703</a> by <a href="https://github.com/berkayozdin"><code>@berkayozdin</code></a> – Make the precompiled Svelte output work on every Svelte 5 runtime</p> <p>Svelte 5.56 changed the <code>exclude</code> argument of the private <code>rest_props</code> runtime helper from an array (<code>exclude.includes(key)</code>) to a <code>Set</code> (<code>exclude.has(key)</code>). The <code>/svelte</code> entry points ship precompiled component code, so output built against one side of that change throws on the other: the currently published packages fail with <code>TypeError: exclude.has is not a function</code> on Svelte >= 5.56, which aborts the render of every EmbedPDF Svelte component.</p> <p>The Svelte build now routes those calls through a wrapper that hands the runtime an <code>exclude</code> value satisfying both contracts, so one published build stays valid across the whole <code>svelte: ">=5 <6"</code> peer range.</p> </li> </ul> <h2><code>@embedpdf/engines</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/models</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/pdfium</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-annotation</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-attachment</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-bookmark</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-capture</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-commands</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-document-manager</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-export</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-form</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/blob/v2.15.0/packages/plugin-interaction-manager/CHANGELOG.md">@embedpdf/plugin-interaction-manager's changelog</a>.</em></p> <blockquote> <h2>2.15.0</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/embedpdf/embed-pdf-viewer/commit/a8faf04b15291c895118b819d7395c3bca8a4959"><code>a8faf04</code></a> chore: version packages</li> <li>See full diff in <a href="https://github.com/embedpdf/embed-pdf-viewer/commits/v2.15.0/packages/plugin-interaction-manager">compare view</a></li> </ul> </details> <br /> Updates `@embedpdf/plugin-pan` from 2.14.4 to 2.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/releases">@embedpdf/plugin-pan's releases</a>.</em></p> <blockquote> <h2>Release v2.15.0</h2> <h2><code>@embedpdf/plugin-selection</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/685">#685</a> by <a href="https://github.com/simonmysun"><code>@simonmysun</code></a> – Add <code>setSelection(range, documentId?)</code> to the selection capability and document scope for programmatically applying or restoring a text selection.</p> <p>It accepts the same <code>SelectionRangeX</code> (<code>{ start, end }</code> glyph pointers) shape emitted by <code>onSelectionChange</code>, so a saved selection can be passed straight back in to restore it; passing <code>null</code> clears the selection. Page geometry is loaded on demand, so the returned task resolves only once the highlight rects are computed. The range is normalized (start/end may be given in any order), invalid input (malformed range, non-integer/negative indices, out-of-bounds pages) is rejected, glyph indices are clamped to the available page geometry, and previously highlighted pages are repainted so switching to a disjoint selection no longer leaves stale highlights behind.</p> </li> </ul> <h2><code>@embedpdf/core</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/703">#703</a> by <a href="https://github.com/berkayozdin"><code>@berkayozdin</code></a> – Make the precompiled Svelte output work on every Svelte 5 runtime</p> <p>Svelte 5.56 changed the <code>exclude</code> argument of the private <code>rest_props</code> runtime helper from an array (<code>exclude.includes(key)</code>) to a <code>Set</code> (<code>exclude.has(key)</code>). The <code>/svelte</code> entry points ship precompiled component code, so output built against one side of that change throws on the other: the currently published packages fail with <code>TypeError: exclude.has is not a function</code> on Svelte >= 5.56, which aborts the render of every EmbedPDF Svelte component.</p> <p>The Svelte build now routes those calls through a wrapper that hands the runtime an <code>exclude</code> value satisfying both contracts, so one published build stays valid across the whole <code>svelte: ">=5 <6"</code> peer range.</p> </li> </ul> <h2><code>@embedpdf/engines</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/models</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/pdfium</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-annotation</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-attachment</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-bookmark</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-capture</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-commands</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-document-manager</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-export</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-form</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/blob/v2.15.0/packages/plugin-pan/CHANGELOG.md">@embedpdf/plugin-pan's changelog</a>.</em></p> <blockquote> <h2>2.15.0</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/embedpdf/embed-pdf-viewer/commit/a8faf04b15291c895118b819d7395c3bca8a4959"><code>a8faf04</code></a> chore: version packages</li> <li>See full diff in <a href="https://github.com/embedpdf/embed-pdf-viewer/commits/v2.15.0/packages/plugin-pan">compare view</a></li> </ul> </details> <br /> Updates `@embedpdf/plugin-print` from 2.14.4 to 2.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/releases">@embedpdf/plugin-print's releases</a>.</em></p> <blockquote> <h2>Release v2.15.0</h2> <h2><code>@embedpdf/plugin-selection</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/685">#685</a> by <a href="https://github.com/simonmysun"><code>@simonmysun</code></a> – Add <code>setSelection(range, documentId?)</code> to the selection capability and document scope for programmatically applying or restoring a text selection.</p> <p>It accepts the same <code>SelectionRangeX</code> (<code>{ start, end }</code> glyph pointers) shape emitted by <code>onSelectionChange</code>, so a saved selection can be passed straight back in to restore it; passing <code>null</code> clears the selection. Page geometry is loaded on demand, so the returned task resolves only once the highlight rects are computed. The range is normalized (start/end may be given in any order), invalid input (malformed range, non-integer/negative indices, out-of-bounds pages) is rejected, glyph indices are clamped to the available page geometry, and previously highlighted pages are repainted so switching to a disjoint selection no longer leaves stale highlights behind.</p> </li> </ul> <h2><code>@embedpdf/core</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/703">#703</a> by <a href="https://github.com/berkayozdin"><code>@berkayozdin</code></a> – Make the precompiled Svelte output work on every Svelte 5 runtime</p> <p>Svelte 5.56 changed the <code>exclude</code> argument of the private <code>rest_props</code> runtime helper from an array (<code>exclude.includes(key)</code>) to a <code>Set</code> (<code>exclude.has(key)</code>). The <code>/svelte</code> entry points ship precompiled component code, so output built against one side of that change throws on the other: the currently published packages fail with <code>TypeError: exclude.has is not a function</code> on Svelte >= 5.56, which aborts the render of every EmbedPDF Svelte component.</p> <p>The Svelte build now routes those calls through a wrapper that hands the runtime an <code>exclude</code> value satisfying both contracts, so one published build stays valid across the whole <code>svelte: ">=5 <6"</code> peer range.</p> </li> </ul> <h2><code>@embedpdf/engines</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/models</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/pdfium</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-annotation</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-attachment</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-bookmark</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-capture</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-commands</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-document-manager</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-export</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-form</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/blob/v2.15.0/packages/plugin-print/CHANGELOG.md">@embedpdf/plugin-print's changelog</a>.</em></p> <blockquote> <h2>2.15.0</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/embedpdf/embed-pdf-viewer/commit/a8faf04b15291c895118b819d7395c3bca8a4959"><code>a8faf04</code></a> chore: version packages</li> <li>See full diff in <a href="https://github.com/embedpdf/embed-pdf-viewer/commits/v2.15.0/packages/plugin-print">compare view</a></li> </ul> </details> <br /> Updates `@embedpdf/plugin-redaction` from 2.14.4 to 2.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/releases">@embedpdf/plugin-redaction's releases</a>.</em></p> <blockquote> <h2>Release v2.15.0</h2> <h2><code>@embedpdf/plugin-selection</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/685">#685</a> by <a href="https://github.com/simonmysun"><code>@simonmysun</code></a> – Add <code>setSelection(range, documentId?)</code> to the selection capability and document scope for programmatically applying or restoring a text selection.</p> <p>It accepts the same <code>SelectionRangeX</code> (<code>{ start, end }</code> glyph pointers) shape emitted by <code>onSelectionChange</code>, so a saved selection can be passed straight back in to restore it; passing <code>null</code> clears the selection. Page geometry is loaded on demand, so the returned task resolves only once the highlight rects are computed. The range is normalized (start/end may be given in any order), invalid input (malformed range, non-integer/negative indices, out-of-bounds pages) is rejected, glyph indices are clamped to the available page geometry, and previously highlighted pages are repainted so switching to a disjoint selection no longer leaves stale highlights behind.</p> </li> </ul> <h2><code>@embedpdf/core</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/703">#703</a> by <a href="https://github.com/berkayozdin"><code>@berkayozdin</code></a> – Make the precompiled Svelte output work on every Svelte 5 runtime</p> <p>Svelte 5.56 changed the <code>exclude</code> argument of the private <code>rest_props</code> runtime helper from an array (<code>exclude.includes(key)</code>) to a <code>Set</code> (<code>exclude.has(key)</code>). The <code>/svelte</code> entry points ship precompiled component code, so output built against one side of that change throws on the other: the currently published packages fail with <code>TypeError: exclude.has is not a function</code> on Svelte >= 5.56, which aborts the render of every EmbedPDF Svelte component.</p> <p>The Svelte build now routes those calls through a wrapper that hands the runtime an <code>exclude</code> value satisfying both contracts, so one published build stays valid across the whole <code>svelte: ">=5 <6"</code> peer range.</p> </li> </ul> <h2><code>@embedpdf/engines</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/models</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/pdfium</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-annotation</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-attachment</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-bookmark</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-capture</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-commands</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-document-manager</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-export</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-form</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/blob/v2.15.0/packages/plugin-redaction/CHANGELOG.md">@embedpdf/plugin-redaction's changelog</a>.</em></p> <blockquote> <h2>2.15.0</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/embedpdf/embed-pdf-viewer/commit/a8faf04b15291c895118b819d7395c3bca8a4959"><code>a8faf04</code></a> chore: version packages</li> <li>See full diff in <a href="https://github.com/embedpdf/embed-pdf-viewer/commits/v2.15.0/packages/plugin-redaction">compare view</a></li> </ul> </details> <br /> Updates `@embedpdf/plugin-render` from 2.14.4 to 2.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/releases">@embedpdf/plugin-render's releases</a>.</em></p> <blockquote> <h2>Release v2.15.0</h2> <h2><code>@embedpdf/plugin-selection</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/685">#685</a> by <a href="https://github.com/simonmysun"><code>@simonmysun</code></a> – Add <code>setSelection(range, documentId?)</code> to the selection capability and document scope for programmatically applying or restoring a text selection.</p> <p>It accepts the same <code>SelectionRangeX</code> (<code>{ start, end }</code> glyph pointers) shape emitted by <code>onSelectionChange</code>, so a saved selection can be passed straight back in to restore it; passing <code>null</code> clears the selection. Page geometry is loaded on demand, so the returned task resolves only once the highlight rects are computed. The range is normalized (start/end may be given in any order), invalid input (malformed range, non-integer/negative indices, out-of-bounds pages) is rejected, glyph indices are clamped to the available page geometry, and previously highlighted pages are repainted so switching to a disjoint selection no longer leaves stale highlights behind.</p> </li> </ul> <h2><code>@embedpdf/core</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/703">#703</a> by <a href="https://github.com/berkayozdin"><code>@berkayozdin</code></a> – Make the precompiled Svelte output work on every Svelte 5 runtime</p> <p>Svelte 5.56 changed the <code>exclude</code> argument of the private <code>rest_props</code> runtime helper from an array (<code>exclude.includes(key)</code>) to a <code>Set</code> (<code>exclude.has(key)</code>). The <code>/svelte</code> entry points ship precompiled component code, so output built against one side of that change throws on the other: the currently published packages fail with <code>TypeError: exclude.has is not a function</code> on Svelte >= 5.56, which aborts the render of every EmbedPDF Svelte component.</p> <p>The Svelte build now routes those calls through a wrapper that hands the runtime an <code>exclude</code> value satisfying both contracts, so one published build stays valid across the whole <code>svelte: ">=5 <6"</code> peer range.</p> </li> </ul> <h2><code>@embedpdf/engines</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/models</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/pdfium</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-annotation</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-attachment</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-bookmark</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-capture</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-commands</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-document-manager</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-export</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h2><code>@embedpdf/plugin-form</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/blob/v2.15.0/packages/plugin-render/CHANGELOG.md">@embedpdf/plugin-render's changelog</a>.</em></p> <blockquote> <h2>2.15.0</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/embedpdf/embed-pdf-viewer/commit/a8faf04b15291c895118b819d7395c3bca8a4959"><code>a8faf04</code></a> chore: version packages</li> <li>See full diff in <a href="https://github.com/embedpdf/embed-pdf-viewer/commits/v2.15.0/packages/plugin-render">compare view</a></li> </ul> </details> <br /> Updates `@embedpdf/plugin-rotate` from 2.14.4 to 2.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/embedpdf/embed-pdf-viewer/releases">@embedpdf/plugin-rotate's releases</a>.</em></p> <blockquote> <h2>Release v2.15.0</h2> <h2><code>@embedpdf/plugin-selection</code><a href="https://github.com/2"><code>@2</code></a>.15.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/embedpdf/embed-pdf-viewer/pull/685">#685</a> by <a href="https://github.com/simonmysun"><code>@simonmysun</code></a> – Add <code>setSelection(range, documentId?)</code> to the selection capability and document scope for programmatically applying or restoring a text selection.</p> <p>It accepts the same <code>SelectionRangeX</code> (<code>{ star... _Description has been truncated_ Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2026-08-20 14:41:25 +00:00
brios	c19926456c	build(deps): update built from source dep versions in Dockerfiles (#7412 ) # Description of Changes PR updates built from source dep versions in Dockerfiles Changes: * Updated `CALIBRE_VERSION` from 9.4.0 to 9.13.0 in `docker/base/Dockerfile`. * Updated `GS_VERSION` (Ghostscript) from 10.06.0 to 10.07.1 in `docker/base/Dockerfile`. * Updated `IM_VERSION` (ImageMagick) from 7.1.2-13 to 7.1.2-29 in `docker/base/Dockerfile`. * Updated `QPDF_VERSION` is already at 12.3.2, no change. * Updated `UNOSERVER_VERSION` from 3.6 to 3.7 in both `docker/base/Dockerfile` and `docker/unoserver/Dockerfile` to align with the client version and avoid wire mismatches. * Updated `TASK_VERSION` from 3.49.1 to 3.52.0 in `docker/embedded/Dockerfile`, `docker/embedded/Dockerfile.fat`, `docker/embedded/Dockerfile.ultra-lite`, and `engine/Dockerfile`. <!-- Please provide a summary of the changes, including: - What was changed - Why the change was made - Any challenges encountered Closes #(issue_number) --> --- ## Checklist ### General - [X] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [X] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [X] I have performed a self-review of my own code - [X] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [X] I have run `task check` to verify linters, typechecks, and tests pass - [X] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-20 14:41:07 +00:00
brios	383710c1d2	style(navigation): improve unsaved changes modal (#7508 ) # Description of Changes Improves the design of the unsaved changes modal. ### New <img width="802" height="466" alt="image" src="https://github.com/user-attachments/assets/f73bc51d-fb30-4075-a516-1aa0007d2735" /> ### Old <img width="908" height="450" alt="image" src="https://github.com/user-attachments/assets/ef004923-4121-4f28-81f8-e3ee3cd68f78" /> <!-- Please provide a summary of the changes, including: - What was changed - Why the change was made - Any challenges encountered Closes #(issue_number) --> --- ## Checklist ### General - [X] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [X] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [X] I have performed a self-review of my own code - [X] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [X] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [X] I have run `task check` to verify linters, typechecks, and tests pass - [X] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-20 14:40:39 +00:00
Ludy	d8fc68a1a7	ci(e2e): use Playwright container for stubbed matrix (#7576 ) # Description of Changes - Use the pinned official Playwright `v1.58.2-noble` container image. - Remove the per-browser `playwright install --with-deps` step from the matrix jobs. - Keep the browser matrix unchanged for independent Chromium, Firefox, and WebKit reporting. - Configure Playwright to use the container's root home directory while directing Docker to a separate configuration path. - Add npm retry and offline-cache settings to reduce transient dependency installation failures. This prevents three matrix jobs from concurrently downloading Playwright browsers and Linux dependencies, reducing network-related CI failures while preserving separate per-browser test results. --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have run `task check` to verify linters, typechecks, and tests pass - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-20 14:21:56 +00:00
Anthony Stirling	96a00cebd1	Pdf ua converter testing (#7301 ) # Description of Changes Adds a PDF/UA converter, an accessibility report, and PDF/A conformance level A. New: `POST /api/v1/convert/pdf/ua` (Convert tool, "PDF/UA" target). Tags an untagged PDF, marks decorative content as artifacts, embeds missing fonts and applies the document-level PDF/UA requirements (title, language, tab order, form-field descriptions), then validates with veraPDF. The `pdfuaid` declaration is written only if validation passes, so a returned file never claims more than it delivers; response headers report whether it was declared, how many checks still fail and how many images still need a description. New: `POST /api/v1/security/accessibility-report`. Reports what fails, what the converter can fix on its own, what needs a person, and lists the figures needing a description with the keys the conversion accepts back. Read-only; does not modify the file. Capped at 100 MB / 2000 pages and weighted `LARGE_WEIGHT`, since it runs a full veraPDF pass plus the converter's layout analysis over every page. PDF/A level A. `pdfa-1a`, `pdfa-2a` and `pdfa-3a` output formats on the existing `/api/v1/convert/pdf/pdfa` endpoint. Level A is level B plus tagging, so the document is tagged after Ghostscript (which discards any structure tree it is given) and the level A claim is written only if veraPDF agrees. Optional `pdfUa=true` additionally declares PDF/UA alongside PDF/A, again only if it validates. Honesty rules the implementation holds to: - Never claim a level that was not reached. If tagging fails, the file is returned at level B and is named `_PDFA-2b.pdf`, not `_PDFA-2a.pdf`. With `strict=true` the request fails outright rather than returning a level B file against a level A request, and a level B pass no longer satisfies a strict level A request. - Never relabel a document's language. The requested language (default `en-GB`) is applied only when the document declares none; a French PDF stays French unless the caller sets `overrideLanguage`, and ignoring a requested language is reported as a warning. - Never invent alternative text. Descriptions come from the caller. The Convert panel can list the images needing one (via the report endpoint) and send them back per figure; any image left undescribed blocks the conformance claim rather than being papered over. - Never certify hidden content. Marking images decorative, or suppressing text that could not be tagged reliably, withdraws the claim instead of passing the checker by hiding content. PDF/UA-1 and PDF/UA-2 are both offered; UA-2 raises the file to PDF 2.0 and namespaces the structure tree, and its test asserts conformance rather than merely reporting it. Convert steps saved in Automations/Pipelines round-trip their PDF/UA settings (profile, language, override, title, font embedding, descriptions). --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have run `task check` to verify linters, typechecks, and tests pass - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-20 12:00:03 +00:00
Anthony Stirling	50d34fcca5	Add download, rename and duplicate to the file actions menu (#7536 ) # Description of Changes Adds expanded dropdown menu for download, rename and duplicate <img width="560" height="380" alt="image" src="https://github.com/user-attachments/assets/84464f0a-46e1-42cf-8098-26f77888710f" /> <img width="560" height="480" alt="image" src="https://github.com/user-attachments/assets/ed871f98-7f89-4560-869e-9ff514000b6f" /> --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have run `task check` to verify linters, typechecks, and tests pass - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-20 11:47:05 +00:00
stirlingbot[bot]	4791d558c5	Update Backend 3rd Party Licenses (#7579 ) Auto-generated by stirlingbot[bot] This PR updates the backend license report based on dependency changes. Signed-off-by: stirlingbot[bot] <stirlingbot[bot]@users.noreply.github.com> Co-authored-by: stirlingbot[bot] <195170888+stirlingbot[bot]@users.noreply.github.com>	2026-08-20 11:16:18 +00:00
Ludy	91fc26f10c	chore: Bump version to 2.14.3 (#7554 ) # Description of Changes This PR bumps the Stirling PDF application version from `2.14.2` to `2.14.3` across the project. Changes include: - Updated the Gradle project version in `build.gradle` to `2.14.3`. - Updated the Tauri desktop application version in `frontend/editor/src-tauri/tauri.conf.json`. - Updated the AUR package version for `stirling-pdf-desktop`. - Updated the AUR package version for `stirling-pdf-server-bin`. - Updated the mocked `appVersion` used by the core frontend server experience simulations. - Updated the mocked `appVersion` used by the proprietary frontend server experience simulations. - Kept all application, desktop, packaging, and test/simulation version references synchronized for the `2.14.3` release. The change prepares the project metadata and packaging configuration for the `2.14.3` release and prevents different components from reporting or packaging the previous `2.14.2` version. --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have run `task check` to verify linters, typechecks, and tests pass - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-20 09:53:28 +00:00
EthanHealy01	f7ed1822c7	Float the editor search when no file is open (#7575 ) ## What The super-search work pinned the editor's `WorkbenchBar` visible on every view except My Files, even with no file open. That left an empty workbench showing a fully painted bar whose only live control was the search — download / close / print / save were all disabled, because those actions only make sense with a file open. This stops forcing the bar. When nothing is open, only the global search floats (unpainted, centered), mirroring how the Processor already works. When a file is open, the `WorkbenchBar` renders exactly as before. Also fixes a smaller Processor issue: its floating search strip was shorter than the sidebar logo row, so the search sat higher than the brand. Its height now matches the logo row (51px) so they line up. ## Changes - `Workbench.tsx` — render the `WorkbenchBar` only when a file is open (or a custom view supplies content); otherwise render the new floating search. My Files and `hideTopControls` custom views are unchanged. - `WorkbenchFloatingSearch.tsx` / `.css` (new) — the editor's `SuperSearch` floated in an unpainted strip, mirroring `PortalSearchBar`. Its vertical band matches the bar's so opening a file swaps in the bar without a shift. - `PortalSearchBar.css` — strip height matched to `.portal-sidebar__logo` (51px) so the Processor search aligns with the logo. The notification bell is intentionally out of scope — it ships in a separate PR. ## Before / after (ignore the bell icon in the after that’s not live yet) <img width="2056" height="1077" alt="Screenshot 2026-08-20 at 2 28 17 AM" src="https://github.com/user-attachments/assets/144f5216-4784-42b2-8c09-afda43577ad0" /> <img width="2056" height="1071" alt="Screenshot 2026-08-20 at 2 28 31 AM" src="https://github.com/user-attachments/assets/63af9303-af8a-48dd-b113-485169fb4924" /> - Editor, no file: painted bar with disabled buttons → just a floating search. - Editor, file open: unchanged. - Processor: search now vertically aligned with the logo. ## Testing - `task frontend:check` — lint (incl. colour linters) + typecheck + tests (247 files / 2137 tests) all pass. - Processor alignment verified in Storybook (`Portal/Shell/AppShell`): logo row, search strip, and search pill share the same vertical center. - Editor float not verified in-browser (local backend is behind a login gate); covered by types/tests and reuses the verified Processor pattern.	2026-08-20 09:33:26 +00:00
James Brunton	a744102cb6	Support Supporting Files in Pipelines (#7547 ) # Description of Changes Currently in the Processor's Pipelines page, none of the tools which require supporting files are usable because it's never been hooked up to the new API to upload supporting files. This PR hooks it up to that so all tools using supporting files work in the processor. I had to tweak the type generation a little for this so we have a static map of which params are for supporting files so we know to handle them differently. The `Test with a file` button has to work a little differently than the main run since it's running an ad-hoc pipeline so the files haven't necessarily been saved to the server yet. In this case, it'll use whatever local changes the user has made for those pipeline steps, and for all other steps, it'll just use what's saved in the server.	2026-08-20 08:23:20 +00:00
stirlingbot[bot]	1690cc25cc	Update Frontend 3rd Party Licenses (#7573 ) Auto-generated by stirlingbot[bot] This PR updates the frontend license report based on changes to package.json dependencies. Signed-off-by: stirlingbot[bot] <stirlingbot[bot]@users.noreply.github.com> Co-authored-by: stirlingbot[bot] <195170888+stirlingbot[bot]@users.noreply.github.com>	2026-08-20 05:15:37 +00:00
Ludy	088e0ef4e2	deps(frontend): upgrade Cantoo PDF library to 2.8.2 (#7493 ) # Description of Changes This pull request upgrades the frontend PDF dependency from `@cantoo/pdf-lib` 2.6.5 to 2.8.2. - Updated `frontend/package.json` to require `@cantoo/pdf-lib` `^2.8.2`. - Regenerated `frontend/package-lock.json` with `@cantoo/pdf-lib@2.8.2`, `pako@2.2.0`, and `node-html-better-parser@1.5.9`. - Added the root npm `pako` override recommended by the upstream release. - The upgrade brings upstream parser, object-stream, encryption, form, PNG, and PDF serialization fixes into the frontend dependency. - No application API migration was required because the project does not use the newly added PDF/A, XFA, Factur-X, incremental-update, fontkit, or page-content-extraction APIs. The main challenge was validating the broad upstream change set against the project's actual usage. The frontend typecheck and a direct PDF create/save/load smoke test passed. The complete `frontend:check` and `frontend:test` tasks exceeded the available execution timeout without reporting a test failure. No related issue. --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/HowToAddNewLanguage.md) (if applicable) - [x] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [x] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#6-testing) for more details.	2026-08-19 18:29:02 +00:00
ConnorYoh	6bae9d516d	chore(saas): one task per environment, and make the frontend follow it (#7483 ) ## The problem The `dev` profile hardcoded one project ref (`qacaivhsjtftfwtgjvva`) in five places: the ref, the Supabase URL, the publishable key, the datasource host and the meter endpoint. That made it both the shared environment everyone relies on and the only thing you could point the backend at. Testing an open SaaS PR meant hand-overriding all five via env just to reach that PR's Supabase preview branch, which is the only place the PR's migrations have actually been applied. Get it wrong and you see `relation "stirling_pdf.<new table>" does not exist` for a table the PR added, which is what happened on [#7414](https://github.com/Stirling-Tools/Stirling-PDF/pull/7414). ## One task per environment ```bash task dev:saas # backend + frontend + engine, against this PR's preview branch task staging:saas # backend + frontend + engine, against the shared v3 project task backend:dev:saas # backend only, preview branch task backend:staging:saas # backend only, v3 ``` \| \| how \| vars \| project \| \|---\|---\|---\|---\| \| prod \| `PROFILES=none` \| `SAAS_DB_` \| the live one \| \| staging \| `PROFILES=staging` \| `SAAS_STAGING_` \| pinned to v3, always there \| \| dev \| `PROFILES=dev` \| `SAAS_DEV_` \| follows a SaaS PR's preview branch \| `PROFILES` is still the underlying switch, so the old spelling keeps working. Production deliberately has no named task: reaching it should take a conscious `PROFILES=none`, not a tab-complete. staging* is the old `dev` configuration, moved and kept pinned. The value of a shared environment is that it is still there tomorrow: reproduce a bug, paste a link to a colleague, share data. dev is parameterised by `SAAS_DEV_PROJECT_REF` and derives the Supabase URL, JWT issuer, JWKS, meter endpoint and (unless overridden) the database host from it. Switching which PR you are testing is one variable instead of five. With no ref set, `task backend:dev:saas` stops and says what to set rather than falling back. ## The frontend was the real gap `frontend/editor/.env` is committed and pins the production Supabase project, and nothing in the frontend knew about dev or staging. So `task dev:saas` gave you a backend on a preview branch and a login against prod, unless you happened to have hand-written `frontend/editor/.env.saas.local`. The dev tasks now read the backend's env files and derive `VITE_SUPABASE_URL` and `VITE_SUPABASE_PUBLISHABLE_DEFAULT_KEY` from the same project ref the backend resolved, so the two halves cannot point at different projects. Nothing to keep in sync by hand, no new vite mode, and `SAAS_ENV=prod` opts back out to the committed values. ## Where to put your local values Two files, both gitignored, neither ever committed: `app/.env.saas.local` is the only one you normally need. The tasks load it for the backend and the frontend. ```bash # staging: everything else is already defaulted, so this is all it takes SAAS_STAGING_DB_PASSWORD=... # dev: the preview branch of the PR you are testing, from its "Supabase Preview" check. # A branch has its OWN password and API keys; the parent project's will not authenticate. SAAS_DEV_PROJECT_REF=... SAAS_DEV_DB_PASSWORD=... SAAS_DEV_PUBLISHABLE_KEY=... # prod, if you ever need it SAAS_DB_PROJECT_REF=... SAAS_DB_URL=... SAAS_DB_PASSWORD=... SUPABASE_EDGE_FUNCTION_SECRET=... ``` `frontend/editor/.env.saas.local` is no longer needed for choosing a Supabase project, and is best left empty or deleted. If you have one from before this PR, note that the task-supplied values now win, which is the point: the frontend follows the backend. A blank is not the same as absent. A dotenv line with an empty value still sets the variable, and Spring's `${VAR:default}` only falls back when a variable is absent. So `.env.saas` lists what you must set as blanks, and leaves out the two `_DB_URL` overrides, which have real defaults to fall back to. This is not theoretical, see below. Committed `app/.env.saas` holds non-secret defaults only. Real secrets are passwords, the edge-function secret and service-role keys. Project refs and publishable keys are neither: a ref is the public `<ref>.supabase.co` subdomain and a publishable key ships in the browser bundle by design, which is why `frontend/editor/.env` has always carried prod's. ## Three bugs found while building the tasks All three were in this PR's own earlier commits, and all three were caught by actually booting things rather than by reading the config. staging could not boot at all.* A blank `SAAS_STAGING_DB_URL=` in `.env.saas` set the variable to empty, so `${SAAS_STAGING_DB_URL:jdbc:...}` resolved to `""` and startup failed with `spring.datasource.url is required when the saas profile is active`. The file already carried a comment warning about exactly this; it had only been applied to the dev block. The original verification for this PR was "placeholders resolve" and "the task parses", neither of which boots anything. The dev to staging fallback ran `ddl-auto=update` against shared v3. The dev profile sets `update`, which is right for a disposable preview branch, and separately fell back to staging's project ref. Together that meant Hibernate was free to reconcile tables that RLS policies depend on. `application-staging.properties` pins `none`, but that only applies when the staging profile is the active one, which it was not on the fallback path. There is no fallback now: with no ref the task stops before gradle, and the frontend fails the same way, both naming the variable. `PROFILES=` never selected production. Go template `default` treats `""` as absent, so it silently resolved back to `dev`. It is `PROFILES=none` now. ## Two choices worth reviewing Staging keeps its committed project ref, now as a `${SAAS_STAGING_PROJECT_REF:...}` default in one place, with the URL, database host and meter endpoint all derived from it. So staging still works with zero setup, and repointing it is one variable. Nothing in CI referenced the ref or the profile. Its publishable key default carries no inline `gitleaks:allow`: a trailing comment in a `.properties` file is part of the value, so the pragma ended up inside the key. It is in `.gitleaksignore` instead. `SAAS_DEV_DB_URL` still overrides the whole URL, so a branch needing the pooler host rather than the direct one is reachable without touching committed config. ## Verification - `task backend:staging:saas` boots against v3 and serves `200`. It could not boot before this commit. - `task backend:dev:saas` with no ref stops before gradle naming the variable, and `PROFILES=none` still reaches production. `task frontend:dev:saas` fails the same way; `SAAS_ENV=staging` still resolves with no local config. - Frontend routing picks the SaaS runner for dev/staging and the plain runner for prod; the derivation returns the right URL and key for each. - Vite's `process.env` precedence and Task's dotenv/env semantics were measured, not assumed. That is how one trap surfaced: Task sets an `env:` key even when its value resolves to empty, and Vite treats an empty `process.env` `VITE_*` as authoritative over a committed `.env`. Putting the Supabase vars on the shared `dev:_run` would have blanked Supabase config for the core, proprietary and desktop dev servers, so the SaaS path has its own runner. - `:saas:spotlessApply` and `:saas:compileJava` green. `DevProfileProjectNotice` becomes `SaasProjectNotice` and covers both profiles, stating the project ref and `ddl-auto` at startup so which environment you are on is never a guess. No behaviour change for prod: the `saas` profile is untouched.	2026-08-19 14:46:00 +00:00
EthanHealy01	0f8803f35f	Require the policy-management role to run a policy against its sources (#7565 ) ## What Running a stored policy against its configured sources (`POST /api/v1/policies/{id}/trigger`, the manual "run now") now requires the policy-management role — global admin self-hosted, team leader on SaaS — alongside the existing team scoping. ## Why A source sweep operates on the team's configured sources using the server's stored connection credentials, so it belongs with the other policy-management capabilities rather than with ordinary use. Team scoping on its own didn't express that distinction. ## Not changed - `POST /{id}/run` — running a policy over documents the caller supplied stays open to every team member. That's ordinary editor enforcement on upload and export, and gating it would break it. - Ad-hoc pipelines (`/run`, `/run/stream`). - The scheduled, folder-watch and webhook triggers. - Single-user deployments (login disabled), which have no roles. ## Implementation `PolicyManagementAuthority` gains `canTriggerPolicies()`, kept separate from `canEditPolicies()` so the two capabilities can diverge later. Both current implementations grant it to the same principals that may edit policies. ## Tests - role absent → 403, rejected before any run starts - role present → 202 - login disabled → check skipped entirely - `/{id}/run` asserted to consult neither authority method, so the gate can't quietly extend to the editor path later	2026-08-19 14:27:39 +00:00
Anthony Stirling	6f7f28946c	Set deployment: false on environment jobs that do not deploy (#7562 ) # Description of Changes thanks ludy for the tip :P --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have run `task check` to verify linters, typechecks, and tests pass - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-19 14:19:26 +00:00
Ludy	ec3de16c08	ci: centralize Gradle caching across GitHub Actions workflows (#7546 ) ## Summary This pull request restructures Gradle dependency caching across the GitHub Actions workflows. The central `gradle-cache-prime` job is responsible for preparing the shared backend Gradle cache. Reusable workflows restore that shared cache without writing to the same key, while independently triggered workflows use isolated cache namespaces. ## What changed ### Shared Gradle cache - Added a stable `gradle-v1-` cache namespace for the shared backend cache. - The cache key includes the runner OS, runner architecture, JDK version, and the relevant Gradle configuration files. - The cache key is calculated before Gradle runs and reused for the later save step. - The prime job performs a lookup first and resolves backend dependencies only when the exact cache is missing. - This prevents Gradle or Spotless changes during the prime step from producing a different save key from the key used by downstream jobs. ### Reusable workflows - Backend, OpenAPI, license, Docker, E2E, and migration workflows restore the shared cache instead of writing to the shared key. - The backend build matrix includes `matrix.jdk-version` in its cache key. - Enterprise, Tauri, and generated-model workflows support the `use_shared_cache` boolean input. - When `use_shared_cache` is enabled, those workflows restore the shared cache. - When it is disabled, they use workflow-specific cache namespaces. ### Independent workflows Independent workflows now use separate cache prefixes, including: - `gradle-license-report-v1-` - `gradle-swagger-v1-` - `gradle-push-docker-v1-` - `gradle-tauri-releases-v1-` - `gradle-deploy-pr-v1-` - `gradle-playwright-e2e-v1-` - `gradle-generated-models-v1-` This prevents them from creating or affecting the shared backend cache before the prime job. ### Build and E2E flow - Removed the `-PnoSpotless` option from the central Gradle dependency-resolution command. - Removed the separate Gradle dependency prime/retry logic from the live E2E workflow. - Connected the Tauri build and generated-models check to the central cache-prime job. ## Motivation Previously, multiple workflows could use and save the same Gradle cache key independently. The first workflow to save the cache could therefore determine its contents, even if it had resolved a different or incomplete set of dependencies. The cache key was also evaluated after some Gradle tasks had run. If Gradle or Spotless modified a file covered by `hashFiles(...)`, the save key could differ from the restore key used by downstream jobs. This change gives the shared cache a single owner, isolates workflow-specific caches, and makes cache usage deterministic across the CI pipeline. ## Expected result - `gradle-cache-prime` is the single writer for the shared backend Gradle cache. - Downstream jobs restore the same cache without competing cache writes. - Independently triggered workflows remain isolated through their own cache namespaces. - Changes to the monitored Gradle configuration files produce a new cache key. - The normal Gradle/Spotless path is included when the shared cache is populated. ## Validation - Compared the cache key expressions and `hashFiles(...)` inputs across the affected workflows. - Verified that the central restore and save steps use the same precomputed key. - CI should confirm that the prime job populates the shared cache and downstream workflows only restore it. ## Checklist - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have performed a self-review of my changes - [ ] I have run the relevant CI checks - [ ] I have tested the workflow changes	2026-08-18 19:25:55 +01:00
EthanHealy01	913601ff03	Consolidate the editor + processor sidebar footers into one component (#7539 ) ## What Both sidebars ended in a different bottom section. The editor showed an account row (avatar, name, settings); the processor showed a "Link Stirling account" CTA plus a `Settings` nav item and no identity at all. They are now one shared `<NavFooter>` rendering the same rows in both apps, in this order: 1. the link-account CTA (self-hosted, when unlinked) 2. free credits remaining 3. Open \<the other app\> 4. the account row — avatar, name, settings It's a single surface with hairline dividers between rows, not stacked cards. Rows are assembled as a list, so a row this build doesn't show (no wallet, no processor access, nothing to link) takes its divider with it rather than leaving a stray line. This also fixes the profile-picture/initials desync between the sidebar and the account settings page. ## Screenshots Captured with the stubbed Playwright harness at 1600x900, scoped to the sidebar and auto-cropped to the region that actually changed. Base is `origin/main`; every state is driven by dummy backend stubs so all the nav-bar permutations are covered. <img width="2104" height="3044" alt="montage_cloud-dark" src="https://github.com/user-attachments/assets/667c9a71-3ab7-4582-9259-08cda521e238" /> <img width="2104" height="3044" alt="montage_cloud-light" src="https://github.com/user-attachments/assets/126bc994-efa3-436b-bf50-31d76f574eaa" /> <img width="2104" height="1492" alt="montage_editor-dark" src="https://github.com/user-attachments/assets/c725726d-ea90-4fa9-bf0a-6014f3729869" /> <img width="2104" height="1490" alt="montage_editor-light" src="https://github.com/user-attachments/assets/d0d34e0a-ac60-4f8c-af15-afb66fbd679e" /> <img width="2104" height="1066" alt="montage_processor-dark" src="https://github.com/user-attachments/assets/51ccfe63-c327-41f4-ab91-74555b6f7148" /> <img width="2104" height="1068" alt="montage_processor-light" src="https://github.com/user-attachments/assets/c90d7aba-90fa-4998-ac8f-26ce666dde71" /> The free-credits meter is a cloud-build surface, so the self-hosted capture can't reach it. Those states come from the new Storybook stories with dummy wallet data (`Shared/NavFooter`), which is also where the credit tone bands and the collapsed rail are easiest to review. ## How it's wired `NavFooter` is purely presentational. Each app resolves its own data through three `@app/` seams, so core carries no build-specific gating and any box whose data is absent is dropped rather than rendered empty. \| Seam \| core \| cloud / proprietary / saas \| \|---\|---\|---\| \| `useFreeCreditsSummary` \| `null` — self-hosted editor installs aren't metered \| cloud reads `freeRemaining` / `freeAllowance` off the same `useWallet()` the Plan page's free meter uses, so the sidebar and Plan can't disagree \| \| `useOtherAppSwitch` \| `null` — core ships no processor \| gated on `portalAccess` (`/api/v1/auth/me` in SaaS, the Spring session flag self-hosted) \| \| Link-account CTA \| n/a \| unchanged conditions — passed in as `accountExtras`, still only when `linkState === "unlinked"`, still a no-op in SaaS \| - The processor reads the meter through its own `@portal/hooks/useFreeCreditsSummary` rather than the editor's `@app` one. Self-hosted resolves `@app/` as proprietary → core, where the cloud wallet hook isn't in the cascade, and the implementation can't live in `proprietary/` because core/desktop builds ship no portal and must never resolve `@portal`. Keeping it in `portal/` gets the figure to the linked self-hosted processor without weakening that rule; it reads the same `GET /api/v1/payg/wallet` the Usage page's trial meter already renders, gated on link state and behind the portal's query cache. `portal-saas/` just re-exports the cloud hook, so both footers share one fetch. The processor-access gate previously lived in two near-identical `AppSwitcher` copies. It moves into `useOtherAppSwitch`, `AppSwitcher` now reads it too, and the duplicate `saas/components/shared/AppSwitcher.tsx` is deleted — the logo switcher and the footer row can no longer disagree about access. ## Profile picture sync One `useAccountIdentity` hook now backs the editor footer, the processor footer and the account settings page. Previously settings derived its initial from `email[0]` while the sidebar used `displayName[0]`, and the two drew different blue discs. Alongside that, the shared `Avatar`: - falls back to initials when a picture URL fails to load, instead of leaving an empty disc - renders one letter for single-word names (`admin` → "A", not "AD") - gains an `xl` size so the settings hero disc is the same component ## Notes - Labelled "Free credits" rather than "free monthly credits": `freeAllowance` is documented as a one-time lifetime grant, not a monthly reset, so "monthly" would misdescribe the data. Happy to change if the backend semantics differ from the type comments. ## Testing - `task frontend:check` and `task frontend:typecheck:all` pass (all 9 build variants). - 9 new `Shared/NavFooter` stories pass the Chromium + axe story scan; `frontend:storybook:a11y:changed` reports no regressions. - Stubbed E2E suite passes, including the `config-button` tour/settings specs that target the account row. Two failures (`console-clean › landing`, `viewer-text-selection › Ctrl+C`) also fail on `origin/main` locally — they need a backend on :8080 and clipboard permissions.	2026-08-18 14:00:43 +00:00
EthanHealy01	cf49742d97	Fix the top bar styling (#7544 ) Every top bar styled itself, so none of them matched the new UI. Also, colors on the premium banner (and possibly others) clashed since the theme changes. ## Before Example Issue <img width="1934" height="348" alt="Screenshot 2026-08-17 at 11 47 20 PM" src="https://github.com/user-attachments/assets/b6f13207-2f47-4084-bd3b-2392f572c1a1" /> ## After (all) <img width="2880" height="800" alt="danger__dark" src="https://github.com/user-attachments/assets/6b311dec-23e7-4059-a6bb-75527cbd2e34" /> <img width="2880" height="800" alt="danger__light" src="https://github.com/user-attachments/assets/3b04b109-5146-4874-88b3-d99770ea51f8" /> <img width="2880" height="800" alt="default-app__dark" src="https://github.com/user-attachments/assets/b0101b98-fce8-467a-99a6-dd40b8864da1" /> <img width="2880" height="800" alt="default-app__light" src="https://github.com/user-attachments/assets/8aa21f01-6549-4d78-b217-c5547d60ab5b" /> <img width="2880" height="800" alt="free-tier-limit__dark" src="https://github.com/user-attachments/assets/07fd7498-f44f-408f-8c79-9b5ea55e13df" /> <img width="2880" height="800" alt="free-tier-limit__light" src="https://github.com/user-attachments/assets/f38c527b-9f64-4db0-b84c-56ca48e464cc" /> <img width="2880" height="800" alt="server-attention__dark" src="https://github.com/user-attachments/assets/447a36fa-056d-4ca9-8b30-04aa0ccd6ed1" /> <img width="2880" height="800" alt="server-attention__light" src="https://github.com/user-attachments/assets/f0311d45-a218-4846-b0ac-47996e2637c5" /> <img width="2880" height="800" alt="team-invitation__dark" src="https://github.com/user-attachments/assets/cc368473-3b9f-4ab0-878a-67da993874c2" /> <img width="2880" height="800" alt="team-invitation__light" src="https://github.com/user-attachments/assets/19d52a3e-4028-46f0-8562-9bd9cef9397a" /> <img width="2880" height="800" alt="upgrade-prompt__dark" src="https://github.com/user-attachments/assets/e9d20daa-f41f-46d9-b827-a84f276e8af1" /> <img width="2880" height="800" alt="upgrade-prompt__light" src="https://github.com/user-attachments/assets/9b6250c1-6a61-40d6-a7ab-e37398d67322" /> ## What changed - `InfoBanner` exposed 8 colour-override props (`background`, `borderColor`, `textColor`, `iconColor`, `buttonColor`, `buttonTextColor`, `closeIconColor`, `buttonVariant`), so every caller invented its own look. Replaced with a closed tone set: `info` · `promo` · `warning` · `danger`. - Tone drives the whole bar — fill, border, icon and the button — so a CTA can't drift from the bar it sits on. Text is neutral in every tone; only the icon carries the tone colour. - All colour comes from `--c-*` tokens mixed over `--c-surface`, so the bars follow light and dark instead of ignoring them. The old bars were hardcoded: in dark mode the two licence warnings stayed cream-on-white. - `promo` keeps the gradient it was always meant to have, built from the existing `--c-hue-indigo`/`--c-hue-purple` stops (documented in `colors.css` as gradient hues, deliberately not accent-following), with the existing `premium` button accent on it. - Deleted the hardcoded colours from all four callers: the purple gradient (`#667eea`→`#764ba2`), the orange soup (`#FFF4E6` / `#9A3412` / `#EA580C`) duplicated across the urgent banner and the admin plan section, and the fixed dark bar (`--mantine-color-dark-7`) on the team invitation. - `UpgradeBanner\|AdminPlanSection` sat on the theme linter's exemption list, which is how those colours survived the theme migration. Exemption removed, so `code-colors` now guards them. - The banner's class was colliding with `core/ui/Banner.css`'s `.sui-banner` (16 live rules), which restyled it in the app but not in Storybook — that's why the two disagreed on radius, border and tone. Renamed to `.app-banner`; the two surfaces now render identically. - Bar is square and full-bleed with a single hairline rule underneath; button labels are optically centred. - Added `--c-warning-subtle`, matching the existing `--c-danger-subtle` / `--c-success-subtle`. - New `Shared → Top bars` story renders all six bars at once, so a change to the shared component is visible against the whole set. - Unrelated one-liner: `frontend/.prettierignore` now ignores the gitignored `editor/screenshots/` capture artifacts, which were failing `format:check` locally. Happy to drop it if you'd rather keep this PR to the bars. ## Testing - `task frontend:check` — typecheck, lint (oxlint + 4 theme-lint passes + stylelint), format, 244 files / 2119 tests. - `frontend:storybook:a11y:changed` — clean in light and dark. - The a11y gate caught a real defect mid-change: giving each banner `role="region"` with the same label produced duplicate landmarks, which the app hits for real whenever two banners show at once. Landmark removed. - All six bars captured in the running editor, light and dark, and diffed against `origin/main`'s component rendered with each caller's original props.	2026-08-18 13:56:47 +00:00
James Brunton	fb70fc13da	Fix tools which crash in the Pipelines page (#7538 ) # Description of Changes Overlay PDFs and Change Metadata both crashed in the Processor because they required `FilesModalContext` and `ViewerContext` respectively. Neither of those contexts make sense to provide in the Processor because there are no files in context and there is no Viewer, so redesign both tool settings to only optionally require these contexts. Their behaviour is unchanged in the Editor but they now work in the Processor (just without the extra info about the active files, since there are none). Also hooks up the Reorganise Pages settings so that it can be used from Automate. The component already existed but just wasn't being used, which just looks like an oversight.	2026-08-18 13:08:23 +00:00
James Brunton	a14eec94ec	Fix corner radius on Mantine checkboxes in Processor (#7537 ) # Description of Changes ## Before <img width="314" height="311" alt="image" src="https://github.com/user-attachments/assets/93239e47-8dd4-4174-8a51-7a4a2494048f" /> ## After <img width="399" height="324" alt="image" src="https://github.com/user-attachments/assets/e2318559-006f-41e4-ac69-8c577ae60b89" />	2026-08-18 09:02:17 +00:00
Anthony Stirling	89d8ffec5d	Ci/environments cleanups, new envs and master to release naming (#7511 ) # Description of Changes Ci/environments cleanups, new envs and master to release naming --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have run `task check` to verify linters, typechecks, and tests pass - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-17 17:49:13 +00:00
EthanHealy01	526bb85e17	Translate the failures debug panel strings (#7500 ) Follow-up to #7296, addressing a missing translation.	2026-08-17 17:00:35 +00:00
James Brunton	99dda7a9f6	Convert Processor tables to be consistent with each other (#7312 ) # Description of Changes Currently, the tables in the processor are inconsistently styled and function differently to each other because they don't all share the same table component. This is a big problem since the Processor is a largely table-based UI and most of most pages in it are tables. This PR creates a new common `DataTable` component and converts all existing tables in the Processor (other than those in the docs pages) to use it, tweaking the individual tables content as necessary so they all work the same. The `DataTable` component is designed to take minimal JSX as arguments. Instead, it takes typed data from the caller and it converts that into JSX, which makes it a lot easier to guarantee that the tables will all render the same and if we want to update the table styling in the future, we just need to do it in one place. I also added sorting capabilities to many of the tables since it was easy with the library and it was appropriate for many of the existing table columns. ## Table Comparisons <img width="2296" height="861" alt="AuditTab-comparison" src="https://github.com/user-attachments/assets/92473508-3f93-45c4-9485-ee21d0d1ecd0" /> <img width="2296" height="617" alt="DocumentExtractions-comparison" src="https://github.com/user-attachments/assets/cf194210-f4c9-42d1-bce1-5a70c0f8fdc5" /> <img width="2296" height="369" alt="InstanceHealthTable-comparison" src="https://github.com/user-attachments/assets/4b048c62-4237-4043-ae89-047df0cd7e60" /> <img width="2296" height="2304" alt="Integrations-comparison" src="https://github.com/user-attachments/assets/9d9edead-8da0-4d49-a249-253579cfdb0e" /> <img width="2296" height="521" alt="InvoicesList-comparison" src="https://github.com/user-attachments/assets/2b6d40b7-d63d-404b-a834-79d5fc62ba9d" /> <img width="2296" height="348" alt="LinkedInstancesTable-comparison" src="https://github.com/user-attachments/assets/fb65c660-baa4-4fcd-8893-05be1962fdab" /> <img width="2296" height="356" alt="PendingInvitations-comparison" src="https://github.com/user-attachments/assets/1f0105ed-b1f8-4e4e-998f-57024875a28f" /> <img width="2296" height="306" alt="PipelinesTable-comparison" src="https://github.com/user-attachments/assets/d84255bd-37f3-4245-b2b5-ef8c06c000ae" /> <img width="2296" height="652" alt="PolicyCatalogue-comparison" src="https://github.com/user-attachments/assets/55f25f20-46f0-47c0-aa40-516cbd5acab5" /> <img width="2296" height="1221" alt="ReviewQueueTable-comparison" src="https://github.com/user-attachments/assets/2206a50c-731f-48cc-958f-aad5e30e47b0" /> <img width="2296" height="344" alt="SourcesTable-comparison" src="https://github.com/user-attachments/assets/76b54efb-54ea-42a8-a0b1-b0cb21f73296" /> <img width="2296" height="659" alt="UsersDirectory-comparison" src="https://github.com/user-attachments/assets/524d1b63-efcf-4ac8-a07d-11aa1849c189" />	2026-08-17 11:47:08 +00:00
ConnorYoh	f15832b2bb	chore(saas): make schema ownership explicit and enforce it (#7489 ) ## The problem The SaaS database has two writers and always has: the Supabase migrations in the SaaS repo, and Hibernate's `ddl-auto`. That was a convention rather than a rule, and it leaked twice. - An older `ddl-auto` run widened `team_memberships.role` to varchar(255), which needed [a dedicated migration](https://github.com/Stirling-Tools/Stirling-PDF-SaaS/blob/v3/supabase/migrations/20260804000000_fix_team_memberships_role_varchar50.sql) to repair, because RLS policies depended on the column. - `payg_instance_usage` shipped with an entity and no migration, and nobody noticed for months — staging already had the table from an earlier `ddl-auto` run. It surfaced only when a fresh preview branch, built from migrations alone, threw `relation does not exist`. Both are the same bug: nobody had to say who owned a table, so the answer got decided by accident. ## The fix `SaasSchemaOwnership` is the register — 29 migration-owned, 29 inherited and left to Hibernate. `MigrationOwnedSchemaFilter` applies it via Hibernate's `hbm2ddl.schema_filter_provider`, wired on the saas profile only. Hibernate is never shown a migration-owned table, so it cannot create, alter, drop or truncate one whatever `ddl-auto` is set to. Inherited tables stay managed, so a fresh preview branch still heals itself on first boot. Self-hosted is untouched — there Hibernate rightly owns everything. Why a filter rather than just `ddl-auto=none`: off, and a fresh branch is missing the 29 inherited tables. On, and Hibernate can reach the other 29. The filter is what lets both be true at once. Why per-table, not per-schema: Hibernate's schema management runs over every mapped entity regardless of namespace. Moving SaaS tables to their own schema would not by itself keep Hibernate out of them — worth knowing, because that was the intuitive fix and it doesn't work. ## The part that makes it stick `SaasSchemaOwnershipTest` makes the register binding: every `@Entity` on the SaaS classpath must appear in exactly one set, so a new entity fails the build until someone states who owns its table. That's the forcing function that would have caught `payg_instance_usage`. I verified it bites rather than assuming it — removing a single entry fails with: ``` These entity tables are not declared in SaasSchemaOwnership, so nobody owns them. Offending tables -> entities: [policies (stirling.software.proprietary.policy.store.PolicyEntity)] ``` naming both the table and the class, which is what the next person actually needs. ## One debatable call The validate filter excludes them too. Letting validation through would flag drift, which is genuinely useful — but `ddl-auto=validate` fails startup, and it would fail on differences we've deliberately accepted (`ai_create_sessions` carries columns from a reverted Typst feature that nothing maps). A boot failure over a table we chose not to manage is noise. Argued in the javadoc; happy to flip it if you'd rather have the signal. ## Dependency Depends on [Stirling-PDF-SaaS#324](https://github.com/Stirling-Tools/Stirling-PDF-SaaS/pull/324), which adds migrations for the four SaaS-owned tables that had none. They're listed here as migration-owned on that basis, so #324 should land first. Companion to [#7483](https://github.com/Stirling-Tools/Stirling-PDF/pull/7483) (dev/staging profiles with per-profile `ddl-auto`). ## Verification `:saas:test` green including the 5 new tests, `spotlessCheck` green, and the mutation check above.	2026-08-17 10:08:09 +00:00
EthanHealy01	08b08aa8a1	Let everyone read the failures they caused (Review Flow PR 3) (#7477 ) Review Flow PR 3. Stacked on #7296. A recorded failure becomes readable by the person who caused it. ## What changes Before this, reading or triaging a failure required leader permissions: `FileRunEventController.requireFailureReviewAllowed()` returned 403 to anyone who could not edit policies. #7296 lets any user report a failure, so they could file into a queue they could never read. That gate is removed from the endpoints and the decision moves into `FileRunEventService`: \| Caller \| Reads and closes \| \|---\|---\| \| Team leader or admin \| the whole team's failures (unchanged) \| \| Anyone else \| only failures where `actor` is them \| \| Team unresolvable \| nothing \| \| Name unresolvable \| nothing \| `GET /kinds` is also opened. It returns static enum metadata, and a member needs it to render failures they can already see. ## Additions - An `actor` predicate on both list queries in `FileRunEventRepository`, threaded through `FileRunEventStore.list`. - `ReadScope` (permitted, teamId, actor) replacing `TeamScope`, with `wholeTeam` / `mine` / `denied` factories. - An actor filter on `dispatch`, so acting on another person's row answers 404, not 403 — the same response as an id that does not exist. ## Fixes - `report()` filed rows under the wrong team. It took the team from the read scope, which returns null for a caller who cannot be named, so such a report landed unteamed in the bucket every team shares. It now uses a dedicated `currentTeamId()`. - `forgetFiles` narrows to the caller even for a leader. File ids are minted by each client, so scoping on team alone would let one caller close a colleague's incidents by naming ids. - The controller no longer injects `PolicyManagementAuthority` or `ApplicationProperties`; with the gate gone it decides nothing. ## Team isolation Unchanged and covered by database-backed tests rather than mocks. `FileRunEventStoreDbTest` asserts that a caller with a team sees only their own team's rows and never the unteamed ones, and that the actor predicate narrows within a team without ever widening across one. Delete either clause from the JPQL and one of those tests fails. No endpoint accepts a team parameter; the team always comes from the authenticated principal. Attribution is fixed here too, because this PR depends on it. A failure's actor was read from the MDC audit principal, which carries the BILLING identity — for a stored policy, always its owner. Since reads are now narrowed to the rows you are the actor on, a wrong actor means the member who caused a failure and holds the document reads nothing, while the policy owner is handed incidents from runs they never triggered. The triggering user is now carried on the run, separate from the billing principal and the output owner, and is null for a trigger-fired sweep so an unattended failure stays ownerless. `PolicyFailureAttributionTest` runs the real engine, recorder, store and service together. The two sides used to assert independently — the engine's test matched the actor with `any()`, which is how this went unnoticed. ## How to test Needs a proprietary or SaaS build with login enabled and two accounts in the same team, one a leader and one not. `task dev:all` gives you the stack. 1. As the member, fail a tool: open a PDF and run Remove Password with a wrong password. 2. Still as the member, go to `/processor/documents` → Failures. Before this PR you got nothing here. Now you see your own row, and only yours. 3. As the leader, open the same view. You see the whole team's rows, including the member's. 4. Member cannot reach a colleague's row. As the leader, copy a row's id from Show raw JSON. As the member, `POST /api/v1/file-run-events/{thatId}/actions/DISMISS`. It answers 404, and the row is untouched — it must not answer 403, which would confirm the row exists. 5. Member can close their own. Dismiss your own row as the member. It leaves the default view. 6. Deleting a file only closes your own rows. As the leader, delete a file in your editor. The member's incidents are untouched even if the leader's client happened to name the same ids. ## Migration None. `actor` is an existing column; this only adds predicates to existing queries.	2026-08-16 22:27:20 +00:00
Ludy	2c89f5fe52	fix(ci): locale path and docs (#7525 ) # Description of Changes Update the TOML locale check to match the current frontend path and align comments/docs with the relocated editor and proprietary source layout. This keeps CI filtering and internal references accurate after the frontend reorganization. --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have run `task check` to verify linters, typechecks, and tests pass - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.	2026-08-16 17:17:16 +01:00
dependabot[bot]	9a90797041	build(deps): bump awsSdkVersion from 2.51.2 to 2.51.3 (#7529 ) Bumps `awsSdkVersion` from 2.51.2 to 2.51.3. Updates `software.amazon.awssdk:s3` from 2.51.2 to 2.51.3 Updates `software.amazon.awssdk:url-connection-client` from 2.51.2 to 2.51.3 Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2026-08-16 17:15:47 +01:00
dependabot[bot]	9c10204cb0	build(deps): bump Swatinem/rust-cache from 2.9.1 to 2.9.2 (#7531 ) Bumps [Swatinem/rust-cache](https://github.com/swatinem/rust-cache) from 2.9.1 to 2.9.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/swatinem/rust-cache/releases">Swatinem/rust-cache's releases</a>.</em></p> <blockquote> <h2>v2.9.2</h2> <h2>What's Changed</h2> <ul> <li>Typofix by <a href="https://github.com/23Skidoo"><code>@23Skidoo</code></a> in <a href="https://redirect.github.com/Swatinem/rust-cache/pull/316">Swatinem/rust-cache#316</a></li> <li>fix: include target names in build/ and .fingerprint/ cleanup by <a href="https://github.com/eitsupi"><code>@eitsupi</code></a> in <a href="https://redirect.github.com/Swatinem/rust-cache/pull/317">Swatinem/rust-cache#317</a></li> <li>fix: include cdylib/rlib/dylib/staticlib targets in build and fingerprint cleanup by <a href="https://github.com/eitsupi"><code>@eitsupi</code></a> in <a href="https://redirect.github.com/Swatinem/rust-cache/pull/320">Swatinem/rust-cache#320</a></li> <li>Scan content of <code>$CARGO_HOME/bin</code> on restore instead of relying on <code>cargo install</code> metadata by <a href="https://github.com/clechasseur"><code>@clechasseur</code></a> in <a href="https://redirect.github.com/Swatinem/rust-cache/pull/325">Swatinem/rust-cache#325</a></li> <li>docs: Update checkout action version to latest by <a href="https://github.com/sondrelg"><code>@sondrelg</code></a> in <a href="https://redirect.github.com/Swatinem/rust-cache/pull/345">Swatinem/rust-cache#345</a></li> <li>Fix Windows cache path validation after Rollup migration by <a href="https://github.com/eitsupi"><code>@eitsupi</code></a> in <a href="https://redirect.github.com/Swatinem/rust-cache/pull/355">Swatinem/rust-cache#355</a></li> <li>fix: support Cargo V2 build dir layout by <a href="https://github.com/claytonwramsey"><code>@claytonwramsey</code></a> in <a href="https://redirect.github.com/Swatinem/rust-cache/pull/371">Swatinem/rust-cache#371</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/23Skidoo"><code>@23Skidoo</code></a> made their first contribution in <a href="https://redirect.github.com/Swatinem/rust-cache/pull/316">Swatinem/rust-cache#316</a></li> <li><a href="https://github.com/eitsupi"><code>@eitsupi</code></a> made their first contribution in <a href="https://redirect.github.com/Swatinem/rust-cache/pull/317">Swatinem/rust-cache#317</a></li> <li><a href="https://github.com/clechasseur"><code>@clechasseur</code></a> made their first contribution in <a href="https://redirect.github.com/Swatinem/rust-cache/pull/325">Swatinem/rust-cache#325</a></li> <li><a href="https://github.com/sondrelg"><code>@sondrelg</code></a> made their first contribution in <a href="https://redirect.github.com/Swatinem/rust-cache/pull/345">Swatinem/rust-cache#345</a></li> <li><a href="https://github.com/claytonwramsey"><code>@claytonwramsey</code></a> made their first contribution in <a href="https://redirect.github.com/Swatinem/rust-cache/pull/371">Swatinem/rust-cache#371</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/Swatinem/rust-cache/compare/v2.9.1...v2.9.2">https://github.com/Swatinem/rust-cache/compare/v2.9.1...v2.9.2</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Swatinem/rust-cache/blob/master/CHANGELOG.md">Swatinem/rust-cache's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <h2>2.9.2</h2> <ul> <li>Fix <code>credentials.toml</code> cleanup</li> <li>Improvements to cleanup, preserving more valid targets</li> <li>Improvements to <code>cargo install</code> handling</li> <li>Correctly sort/dedupe Rust versions</li> </ul> <h2>2.9.1</h2> <ul> <li>Fix regression in hash calculation</li> </ul> <h2>2.9.0</h2> <ul> <li>Update to <code>node24</code></li> <li>Support running from within a <code>nix</code> shell</li> <li>Consider all installed toolchains for cache key</li> <li>Use case-insensitive comparison to determine exact cache hit</li> </ul> <h2>2.8.2</h2> <ul> <li>Don't overwrite env for cargo-metadata call</li> </ul> <h2>2.8.1</h2> <ul> <li>Set empty <code>CARGO_ENCODED_RUSTFLAGS</code> when retrieving metadata</li> <li>Various dependency updates</li> </ul> <h2>2.8.0</h2> <ul> <li>Add support for <code>warpbuild</code> cache provider</li> <li>Add new <code>cache-workspace-crates</code> feature</li> </ul> <h2>2.7.8</h2> <ul> <li>Include CPU arch in the cache key</li> </ul> <h2>2.7.7</h2> <ul> <li>Also cache <code>cargo install</code> metadata</li> </ul> <h2>2.7.6</h2> <ul> <li>Allow opting out of caching $CARGO_HOME/bin</li> <li>Add runner OS in cache key</li> <li>Adds an option to do lookup-only of the cache</li> </ul> <h2>2.7.5</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/Swatinem/rust-cache/commit/6323deb102c322ba6fcbdcafc7e3dddab59af2b6"><code>6323deb</code></a> 2.9.2</li> <li><a href="https://github.com/Swatinem/rust-cache/commit/b16e8d71b289c3b8fc03fc09764563df03712036"><code>b16e8d7</code></a> bump rollup and rebuild</li> <li><a href="https://github.com/Swatinem/rust-cache/commit/3bf42ac996de475743278f3187c4fd89f23b8630"><code>3bf42ac</code></a> invert target/profile check in cleanup</li> <li><a href="https://github.com/Swatinem/rust-cache/commit/6e5b278ead409e28cd5a784014d7ce55007a81d2"><code>6e5b278</code></a> correctly sort and dedupe Rust versions</li> <li><a href="https://github.com/Swatinem/rust-cache/commit/5adc05f6aaa7c92756cb2e2c9b7b3c1d0df9312b"><code>5adc05f</code></a> Bump the actions group across 1 directory with 3 updates (<a href="https://redirect.github.com/swatinem/rust-cache/issues/368">#368</a>)</li> <li><a href="https://github.com/Swatinem/rust-cache/commit/66b1e9526150e74ddd7e4190356facd783fb3b44"><code>66b1e95</code></a> fix: support Cargo V2 build dir layout (<a href="https://redirect.github.com/swatinem/rust-cache/issues/371">#371</a>)</li> <li><a href="https://github.com/Swatinem/rust-cache/commit/72d126e709cad40056a62344eee609d696d62d33"><code>72d126e</code></a> Merge pull request <a href="https://redirect.github.com/swatinem/rust-cache/issues/367">#367</a> from Swatinem/dependabot/npm_and_yarn/dev-patch-2b495...</li> <li><a href="https://github.com/Swatinem/rust-cache/commit/48968d2131215f1c516b89399d23900d554f71fa"><code>48968d2</code></a> Bump the dev-patch group with 2 updates</li> <li><a href="https://github.com/Swatinem/rust-cache/commit/9f151aca7c3990bab7afe2d82ac58088d3b01074"><code>9f151ac</code></a> update dependencies, rebuild</li> <li><a href="https://github.com/Swatinem/rust-cache/commit/0e24e5dcecfbbdcea69e0f528cab00df34fbd231"><code>0e24e5d</code></a> Bump the actions group across 1 directory with 6 updates (<a href="https://redirect.github.com/swatinem/rust-cache/issues/364">#364</a>)</li> <li>Additional commits viewable in <a href="https://github.com/swatinem/rust-cache/compare/c19371144df3bb44fab255c43d04cbc2ab54d1c4...6323deb102c322ba6fcbdcafc7e3dddab59af2b6">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=Swatinem/rust-cache&package-manager=github_actions&previous-version=2.9.1&new-version=2.9.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2026-08-16 17:15:37 +01:00
dependabot[bot]	beea37cb92	build(deps): bump step-security/harden-runner from 2.20.0 to 2.20.1 (#7466 ) Bumps [step-security/harden-runner](https://github.com/step-security/harden-runner) from 2.20.0 to 2.20.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/step-security/harden-runner/releases">step-security/harden-runner's releases</a>.</em></p> <blockquote> <h2>v2.20.1</h2> <h2>What's Changed</h2> <ul> <li>AWS CodeBuild-hosted runner support</li> <li>Implicitly allow single-labeled (internal) domains in block-mode</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/step-security/harden-runner/compare/v2.20.0...v2.20.1">https://github.com/step-security/harden-runner/compare/v2.20.0...v2.20.1</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/step-security/harden-runner/commit/b09bb98e06d4d774595224525879c09bc6e98c40"><code>b09bb98</code></a> Merge pull request <a href="https://redirect.github.com/step-security/harden-runner/issues/680">#680</a> from step-security/aws-code-build</li> <li><a href="https://github.com/step-security/harden-runner/commit/35cd77bcf669054f67ffd3d2802ee54a4f13b5b6"><code>35cd77b</code></a> docs: document the Global Block List in the features list</li> <li><a href="https://github.com/step-security/harden-runner/commit/bb6dbef4bf53876cd2710acd1d36413620d20fb3"><code>bb6dbef</code></a> chore: rebuild dist with clean dependency install</li> <li><a href="https://github.com/step-security/harden-runner/commit/98f73c5a0d2b2cc518e6fb8d973a0a4dde00ba13"><code>98f73c5</code></a> chore: update eBPF agent to v1.8.14</li> <li><a href="https://github.com/step-security/harden-runner/commit/54193c17a4fa3883977217b9afe20378ebe60b19"><code>54193c1</code></a> Reapply "feat(runners): detect AWS CodeBuild-hosted runners as third-party pr...</li> <li><a href="https://github.com/step-security/harden-runner/commit/d22dd481cea4e96cedde031cfe600c248b592d54"><code>d22dd48</code></a> Revert "fix(self-hosted): flush agent events at job end when deploy-on-self-h...</li> <li><a href="https://github.com/step-security/harden-runner/commit/0ff09412fb572363b483a3c86ffe52fe61d9fd19"><code>0ff0941</code></a> fix(self-hosted): flush agent events at job end when deploy-on-self-hosted-vm...</li> <li><a href="https://github.com/step-security/harden-runner/commit/a3c333d110c8d95f34488a22e0e56742cfb1b14f"><code>a3c333d</code></a> Revert "feat(runners): detect AWS CodeBuild-hosted runners as third-party pro...</li> <li><a href="https://github.com/step-security/harden-runner/commit/bf94c00d6bba2ae7c4a479b86653039811569968"><code>bf94c00</code></a> feat(runners): detect AWS CodeBuild-hosted runners as third-party provider</li> <li><a href="https://github.com/step-security/harden-runner/commit/514522c5e449f9e28fc901f770e08a573d413e67"><code>514522c</code></a> fix(self-hosted): resolve runner user when USER env var is unset</li> <li>See full diff in <a href="https://github.com/step-security/harden-runner/compare/bf7454d06d71f1098171f2acdf0cd4708d7b5920...b09bb98e06d4d774595224525879c09bc6e98c40">compare view</a></li> </ul> </details> <br /> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2026-08-16 14:18:51 +01:00

1 2 3 4 5 ...