Auxiliary PDF Render Service 0.1.25 Stable (2026-08-25)

Version?Type?Release Date?Config.Changes?
0.1.25Stable2026-08-25No

Download: https://hub.docker.com/r/humio/pdf-render-service

Updates

Upgrades

Changes that may occur or be required during an upgrade.

  • Installation and Deployment

    • Added body-parser resolution to upgrade transitive dependency from 2.2.2 to 2.3.0 to address CVE-2026-12590.

    • Updated puppeteer from 24.39.1 to 25.3.0.

    • Rebuilt image to pick up latest Alpine package updates.

    • Added ip-address resolution to upgrade transitive dependency from 10.2.0 to 10.4.0 to address CVE-2026-54272, CVE-2026-69192 and CVE-2026-69198.

    • Added basic-ftp resolution to upgrade transitive dependency from 5.3.0 to 5.3.1 to address CVE-2026-44240.

Improvements, new features and functionality

  • Configuration

    • Added the ALLOW_SECRETS_IN_LOGS environment variable (defaults to false). When set to true together with DEBUG=true, logs can contain access tokens used by the service to access report data. This is useful for an operator debugging the integration between the service and LogScale. It requires DEBUG=true since those lines are logged at DEBUG level and are not emitted without it — INFO and ERROR output stays redacted, meaning potential sensitive data is replaced with a placeholder regardless of this setting, so a service running unattended cannot emit credentials even if the flag is left on. Setting it logs a warning that the resulting log must be treated as a secret, and setting it without DEBUG=true logs a warning that it will have no effect.

    • The environment variables LOG_LEVEL and LOG_FORMAT have been added to enable verbose or debug logging without also switching output to the CLI format. Previously setting the environment variable DEBUG to true changed both at once, making verbose logging in production break log ingestion. DEBUG continues to work as before when the new variables are unset.

Bug Fixes

  • Administration

    • Fixed report requests hanging for the full 30 minutes render timeout when the report page returned an HTTP error or a redirect. Now instead it fails fast and logs diagnostics that can be used to debug what went wrong.

Improvement

  • Administration

    • When the report ready marker is never found, the browser's current URL, page title and a snippet of the page body are now logged and the URL and title included in the message sent back to LogScale. This distinguishes a misconfigured or redirecting public URL from a report that is genuinely slow to render, which previously produced identical timeout errors. Content and query strings are redacted in order not to expose secrets, unless it is allowed by enabling ALLOW_SECRETS_IN_LOGS.