Skip to content

fix(container): update image ghcr.io/alam00000/bentopdf ( 2.8.4 ➔ 2.8.5 )#2014

Open
nerdz-bot[bot] wants to merge 1 commit into
mainfrom
renovate/ghcr.io-alam00000-bentopdf-2.x
Open

fix(container): update image ghcr.io/alam00000/bentopdf ( 2.8.4 ➔ 2.8.5 )#2014
nerdz-bot[bot] wants to merge 1 commit into
mainfrom
renovate/ghcr.io-alam00000-bentopdf-2.x

Conversation

@nerdz-bot
Copy link
Copy Markdown
Contributor

@nerdz-bot nerdz-bot Bot commented May 23, 2026

This PR contains the following updates:

Package Update Change
ghcr.io/alam00000/bentopdf patch 2.8.42.8.5

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

alam00000/bentopdf (ghcr.io/alam00000/bentopdf)

v2.8.5: Bug Fixes - v2.8.5

Compare Source

Dad Joke Of the Release

What's the easiest building to lift? A lighthouse 🤣

(This release is later than I would have liked. The past few weeks I've been under the weather and pretty burnt out, so v2.8.5 sat finished for longer than it should have. Thanks for being patient ❤️)

What's Changed
1. Custom Rotate
  • Improved angle input handling, rotation utilities, and a smoother UX for fine-grained rotation. Thanks to @​quhxl for the contribution.
2. Alternate & Mix Pages
  • Alternate and mix pages are now in workflow builder. Fixes #​684
3. Helm Chart Auto Update
  • Helm chart version now auto updates with each release. Fixes #​680
4. New Option in Merge
  • By default merge tool used to keep Keep original page labels from each file intact. Now users have the option to opt out from it via a checkbox. Fixes #​676
Bug Fixes 🐛
  • OCR Arabic + Latin — Fixed mixed Arabic and Latin OCR output where English text appeared as empty boxes when run alongside Arabic. Dual font loading now covers any non Latin script combined with Latin. Also fixes the bug in #​724

  • HEIC in workflow — HEIC images are now correctly accepted in the image to pdf workflow node. Fixes #​703

  • Email parsing reliability — MsgReader CJS/ESM interop fix for .msg files. Fixes #​701

  • Sign PDF signature editor width — Editor now fills the full available width like the rest of the tool. Fixes #​653

  • PDF Compare export issue - Now export correctly filters out instead of showing all the changes in exported PDF. Fixes #​655

  • RFC 3161 error - Now users can correctly timestamp using RFC 3161. Fixes #​649

  • .mjs MIME errors on self-hosted nginx — Vite now emits .js instead of .mjs for built assets, so PDFs no longer fail to load on self-hosted setups whose mime.types doesn't include a .mjs → application/javascript mapping. Fixes the failures reported by users on the Proxmox helper script.

A note on canonicals

A lot of BentoPDF users come to and use bentopdf.com directly since the whole thing runs in the browser. Over the past few months I've received complaints from people who searched for BentoPDF and ended up on someone else's self hosted instance instead of the main site. Sometimes that worked out, but more often it confused users and put unwanted traffic on a self hoster who never asked for it.

To address this, canonical URLs, hreflang, and the sitemap now default to bentopdf.com unless explicitly overridden. This only affects deployments that are exposed to the public internet. Internal and private self-hosted instances (anyone running with ROBOTS_NOINDEX=true) are unaffected, since search engines were never indexing those pages to begin with.

The change fixes three things at once:

  1. Self-hosters keep their bandwidth. Public-facing self-hosted instances no longer absorb search traffic from people who were actually looking for bentopdf.com.
  2. Users land on the right site. Search results for "BentoPDF" reliably point to bentopdf.com instead of a randomly indexed mirror.
  3. Self-hosters who want their own canonical can still claim it. Build with --build-arg SITE_URL=https://your-domain.com and canonicals, sitemap, and hreflang all point at your domain. Documented in STATIC-HOSTING.md.
Self-Hosting Docs

The bentopdf-simple was meant to be used for self hosting, while the bentopdf image is used on our live site. But unfortunately many users still run the bentopdf build

  • Self-Hosted vs Commercial builds — Docs now clearly distinguish the bentopdf-simple (Self-Hosted) and bentopdf (Commercial) builds across the README, getting-started, docker.md, and self-hosting/index.md. Self Hosted is the recommended default; the existing Commercial path is unchanged.
  • New "Common Issues" troubleshooting section — Added .mjs MIME entries and SharedArrayBuffer / COEP-COOP entries to the self-hosting docs, with platform-specific snippets for nginx, Apache, AWS S3, and Kubernetes.
Looking ahead: a bundled self-host build

Something I'm looking into: bringing back a fully bundled self host image like earlier versions had. The current setup pulls the heavy AGPL libraries (PyMuPDF, Ghostscript, CoherentPDF) from jsDelivr at runtime, which works but is sometimes cumbersome for self hosters to manage. Packaging this cleanly under the dual license takes some thought, so no timeline yet. But for the self hosters who've asked about it, it's on my mind and I am working on it so there's no friction going forward.

A note from the developer

Translations across the 19 locales are still automated through Microsoft Translator for the bulk passes. Native-speaker corrections like the ones @​Stephan-P keeps catching are the only thing keeping short-string quality high. A Crowdin or Weblate workflow is on the roadmap so corrections reach a reviewer before they ship. Until then, if you read any of the supported languages and spot something off, a PR or even a quick issue is genuinely appreciated.

By the Community
New Contributors

Full Changelog: alam00000/bentopdf@v2.8.4...v2.8.5

That's it for now. Thank you for using BentoPDF. Have a great weekend! ❤️

v2.8.5: Bug Fixes - v2.8.5

Compare Source

Dad Joke Of the Release

What's the easiest building to lift? A lighthouse 🤣

(This release is later than I would have liked. The past few weeks I've been under the weather and pretty burnt out, so v2.8.5 sat finished for longer than it should have. Thanks for being patient ❤️)

What's Changed
1. Custom Rotate
  • Improved angle input handling, rotation utilities, and a smoother UX for fine-grained rotation. Thanks to @​quhxl for the contribution.
2. Alternate & Mix Pages
  • Alternate and mix pages are now in workflow builder. Fixes #​684
3. Helm Chart Auto Update
  • Helm chart version now auto updates with each release. Fixes #​680
4. New Option in Merge
  • By default merge tool used to keep Keep original page labels from each file intact. Now users have the option to opt out from it via a checkbox. Fixes #​676
Bug Fixes 🐛
  • OCR Arabic + Latin — Fixed mixed Arabic and Latin OCR output where English text appeared as empty boxes when run alongside Arabic. Dual font loading now covers any non Latin script combined with Latin. Also fixes the bug in #​724

  • HEIC in workflow — HEIC images are now correctly accepted in the image to pdf workflow node. Fixes #​703

  • Email parsing reliability — MsgReader CJS/ESM interop fix for .msg files. Fixes #​701

  • Sign PDF signature editor width — Editor now fills the full available width like the rest of the tool. Fixes #​653

  • PDF Compare export issue - Now export correctly filters out instead of showing all the changes in exported PDF. Fixes #​655

  • RFC 3161 error - Now users can correctly timestamp using RFC 3161. Fixes #​649

  • .mjs MIME errors on self-hosted nginx — Vite now emits .js instead of .mjs for built assets, so PDFs no longer fail to load on self-hosted setups whose mime.types doesn't include a .mjs → application/javascript mapping. Fixes the failures reported by users on the Proxmox helper script.

A note on canonicals

A lot of BentoPDF users come to and use bentopdf.com directly since the whole thing runs in the browser. Over the past few months I've received complaints from people who searched for BentoPDF and ended up on someone else's self hosted instance instead of the main site. Sometimes that worked out, but more often it confused users and put unwanted traffic on a self hoster who never asked for it.

To address this, canonical URLs, hreflang, and the sitemap now default to bentopdf.com unless explicitly overridden. This only affects deployments that are exposed to the public internet. Internal and private self-hosted instances (anyone running with ROBOTS_NOINDEX=true) are unaffected, since search engines were never indexing those pages to begin with.

The change fixes three things at once:

  1. Self-hosters keep their bandwidth. Public-facing self-hosted instances no longer absorb search traffic from people who were actually looking for bentopdf.com.
  2. Users land on the right site. Search results for "BentoPDF" reliably point to bentopdf.com instead of a randomly indexed mirror.
  3. Self-hosters who want their own canonical can still claim it. Build with --build-arg SITE_URL=https://your-domain.com and canonicals, sitemap, and hreflang all point at your domain. Documented in STATIC-HOSTING.md.
Self-Hosting Docs

The bentopdf-simple was meant to be used for self hosting, while the bentopdf image is used on our live site. But unfortunately many users still run the bentopdf build

  • Self-Hosted vs Commercial builds — Docs now clearly distinguish the bentopdf-simple (Self-Hosted) and bentopdf (Commercial) builds across the README, getting-started, docker.md, and self-hosting/index.md. Self Hosted is the recommended default; the existing Commercial path is unchanged.
  • New "Common Issues" troubleshooting section — Added .mjs MIME entries and SharedArrayBuffer / COEP-COOP entries to the self-hosting docs, with platform-specific snippets for nginx, Apache, AWS S3, and Kubernetes.
Looking ahead: a bundled self-host build

Something I'm looking into: bringing back a fully bundled self host image like earlier versions had. The current setup pulls the heavy AGPL libraries (PyMuPDF, Ghostscript, CoherentPDF) from jsDelivr at runtime, which works but is sometimes cumbersome for self hosters to manage. Packaging this cleanly under the dual license takes some thought, so no timeline yet. But for the self hosters who've asked about it, it's on my mind and I am working on it so there's no friction going forward.

A note from the developer

Translations across the 19 locales are still automated through Microsoft Translator for the bulk passes. Native-speaker corrections like the ones @​Stephan-P keeps catching are the only thing keeping short-string quality high. A Crowdin or Weblate workflow is on the roadmap so corrections reach a reviewer before they ship. Until then, if you read any of the supported languages and spot something off, a PR or even a quick issue is genuinely appreciated.

By the Community
New Contributors

Full Changelog: alam00000/bentopdf@v2.8.4...v2.8.5

That's it for now. Thank you for using BentoPDF. Have a great weekend! ❤️


Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

@github-actions
Copy link
Copy Markdown

no HelmRelease objects found in cluster

@nerdz-bot nerdz-bot Bot force-pushed the renovate/ghcr.io-alam00000-bentopdf-2.x branch 24 times, most recently from 3086483 to 5da1fed Compare May 29, 2026 23:29
@nerdz-bot nerdz-bot Bot force-pushed the renovate/ghcr.io-alam00000-bentopdf-2.x branch 2 times, most recently from 619be14 to 953e292 Compare May 30, 2026 05:17
@nerdz-bot nerdz-bot Bot force-pushed the renovate/ghcr.io-alam00000-bentopdf-2.x branch from 953e292 to e903dbb Compare May 30, 2026 11:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants