Skip to content

Changelog

What shipped, and when.

A plain-English summary of NextPDF Core releases. Every entry maps to a real tagged release in the engineering changelog; the full, exhaustive history lives in the repository.

See the dev → GA storyTry the latest
  1. UnreleasedIn development

    In development — signing depth, vertical writing modes, API freeze

    • High-level PAdES signing end to end: setSignature() now produces CMS-verifiable signed PDFs at B-B, with B-T (RFC 3161 timestamp) and the long-term B-LT / B-LTA levels (DSS + document timestamps) driven through the same seam.
    • Vertical writing modes (vertical-lr) promoted toward a Stable default, with OpenType vert / vrt2 GSUB binding.
    • Conic gradients render as a canonical Type-4 Gouraud mesh via the /sh operator.
    • Public-API freeze: the Inspector, RFC 5280 PKI path-validation, and RAG vector-index SPIs graduate to a frozen, stable contract.
    Breaking
    • The next major (v7.0.0) flips remaining behavioural defaults on and silences v6 deprecation notices; a customer-side preflight scanner (composer v7:preflight) flags every affected call site.
  2. 6.0.0Major

    First major release — modern CSS layout, on by default

    • CSS Grid, Container Queries, and Subgrid promoted from Beta to Stable and enabled by default.
    • ~93% of the targeted CSS surface now live on the default rendering path; PHPStan Level 10 across the source tree with zero errors.
    • A migration guide and a preflight scanner (composer v6:preflight) enumerate every affected call site before you upgrade.
    Breaking
    • The Grid / Subgrid / Container-Query feature flags now default to on. The v5.x behaviour is a one-line opt-out (CssFeatureFlags::safeMode()).
  3. 5.0.0Major

    Typography, post-quantum signing, and e-invoicing groundwork

    • Vertical CJK, tate-chu-yoko, and Ruby annotation typography.
    • Post-quantum signer interfaces (FIPS 204 ML-DSA, FIPS 205 SLH-DSA) and an RFC 3161 + RFC 5816 timestamp-token verifier for PAdES B-T.
    • EN 16931 / Factur-X / ZUGFeRD governance, a PDF/R-1 (ISO 23504-1) raster profile, and the UAX #9 bidirectional resolver.
    • Reproducible builds and an Arlington PDF Model report-only validator in CI.
    Breaking
    • PDF/UA-2 output defaults to strict conformance; the lenient mode remains as a deprecated opt-out.
  4. 3.0.0Major

    A typed exception taxonomy and a decomposed HTML parser

    • Typed, context-carrying domain exceptions — every failure is a specific, catchable type with structured context for your logs.
    • The HTML parser was decomposed from a 3,876-line monolith into a 1,523-line orchestrator plus 14 focused collaborators.
    • PHP support pinned to >=8.4 <9.0; GitHub Actions SHA-pinned for supply-chain integrity; RFC 6266 / 5987 filename sanitisation.
  5. 2.0.0Major

    The NextPDF name

    • The engine took its NextPDF identity: the NextPDF\* namespace, the nextpdf/core package, and the nextpdf-labs organization.
    • PdfMerger, PageRange, and MergeResult moved into the open-source Core.
    Breaking
    • Namespace and package rename — a mechanical find-and-replace, documented in a complete migration guide.
  6. 1.7.0Minor

    Worker-safe architecture and PHPStan Level 10

    • An immutable Config, a process-lifetime FontRegistry and ImageRegistry, and a DocumentFactory built for long-running workers (Octane, Swoole, RoadRunner).
    • Static analysis raised from PHPStan Level 8 to Level 10 (max) with zero errors; a veraPDF CI workflow and a benchmark suite landed.
  7. 1.6.0Minor

    A production Docker base image

    • A multi-target Dockerfile producing FPM (web) and CLI (queue worker) variants from a single source.
  8. 1.2.0Foundation

    First public release

    • The PDF 2.0 generation core, HTML-to-PDF rendering, and the foundation every edition and adapter builds on.

This is a curated public summary. The complete, commit-level engineering changelog — including audit-remediation and security-hardening detail — ships in the source repository underCHANGELOG.md. Want the story behind the releases? Read the news stream. Looking ahead instead? See the roadmap.