Changelog
Changelog
Section titled “Changelog”The NextPDF ecosystem spans many packages and repositories. This page shows how the ecosystem records change and where each package keeps its own changelog. Use it as an index and a conventions reference, not as a restatement of every commit. Each package keeps its authoritative released changelog in its own repository. The summary table aggregates only the category of change per released version, derived from each repository’s Conventional Commits history.
As a documentation index, this page does not make behavioral claims about any package. To see the rules each package follows when it writes commits and cuts releases, see Changelog conventions.
How change is recorded
Section titled “How change is recorded”Every public NextPDF repository follows two contracts:
- Conventional Commits 1.0.0 —
each commit subject uses the form
type(scope): description, wheretypeis one offeat,fix,perf,refactor,docs,test,build,ci,chore, orrevert. A!after the type/scope, or aBREAKING CHANGE:footer, marks an incompatible change. Security-relevant fixes are tagged so you can filter them. - Semantic Versioning 2.0.0 — a
featraises the minor version, afix/perfraises the patch version, and a breaking change raises the major version. The releasedCHANGELOG.mdin each repository groups human-readable entries by version, using the Keep a Changelog sections.
The summary below covers only user-facing categories: feat (new
capability), fix (corrected behavior), perf (performance), security
(security-relevant fix), and breaking changes. Internal-only commit types
(docs, test, ci, chore, refactor) are left out of the cross-repo
summary on purpose. They do not change what you observe when you use the
package.
Where each package’s changelog lives
Section titled “Where each package’s changelog lives”The authoritative prose changelog for a package is the CHANGELOG.md in that
package’s own repository, grouped by released version. For the full entry text,
use the repository’s release page or its CHANGELOG.md. This index does not
duplicate that text.
| Package | Repository | Authoritative changelog |
|---|---|---|
nextpdf/core | nextpdf | CHANGELOG.md (Keep a Changelog) |
nextpdf/server | nextpdf-server | CHANGELOG.md |
nextpdf/laravel | nextpdf-Laravel | CHANGELOG.md |
nextpdf/symfony | nextpdf-Symfony | CHANGELOG.md |
nextpdf/codeigniter | nextpdf-CodeIgniter | CHANGELOG.md |
nextpdf/artisan | nextpdf-Artisan | CHANGELOG.md |
nextpdf/gotenberg | nextpdf-Gotenberg | CHANGELOG.md |
nextpdf/cloudflare | nextpdf-Cloudflare | CHANGELOG.md |
nextpdf/compat-legacy | nextpdf-compat-tcpdf | CHANGELOG.md |
nextpdf (Python bindings) | nextpdf-python | CHANGELOG.md |
Cross-repo summary — categories per latest released version
Section titled “Cross-repo summary — categories per latest released version”This read-only table is generated from each repository’s Conventional Commits
history at its latest released tag. It counts the user-facing categories and
reports only category counts — never raw commit subjects — so it does not
surface internal identifiers, branch names, or planning references. For the
prose detail behind any line, follow the package’s own CHANGELOG.md.
| Package | Latest released | New capability (feat) | Fixes (fix) | Performance (perf) | Security | Breaking |
|---|---|---|---|---|---|---|
nextpdf/core | v5.2.0 | 317 | 290 | 1 | 1 | yes |
nextpdf/server | v0.1.0 | 15 | 16 | 0 | 0 | no |
nextpdf/laravel | v0.1.0 | 1 | 8 | 0 | 0 | no |
nextpdf/symfony | v0.1.0 | 1 | 7 | 0 | 0 | no |
nextpdf/codeigniter | v0.1.0 | 1 | 10 | 0 | 0 | no |
nextpdf/artisan | v0.1.0 | 1 | 7 | 0 | 0 | no |
nextpdf/gotenberg | v0.1.0 | 0 | 6 | 0 | 0 | no |
nextpdf/cloudflare | v0.1.0 | 0 | 8 | 0 | 0 | no |
nextpdf/compat-legacy | v0.1.0 | 1 | 8 | 0 | 0 | no |
nextpdf (Python) | v1.1.0 | 7 | 5 | 0 | 0 | no |
The counts are cumulative through the named tag. For each integration package, the first tagged release includes its full pre-1.0 history. The
nextpdf/core“Breaking” cell readsyesbecause the core engine has shipped breaking major versions. The per-version details and migration path for each one live in the core repository’sCHANGELOG.mdand itsmigration/guides. This index does not restate them.
What this page deliberately leaves out
Section titled “What this page deliberately leaves out”To keep the public changelog free of internal leakage, this index never surfaces any of the following:
- raw commit subjects or bodies;
- internal issue, ticket, cycle, wave, or work-item identifiers;
- private branch names or unreleased work in progress;
- roadmap or unannounced features;
- contributor automation attribution.
A change appears here only after it becomes part of a released, tagged version of a public package. Unreleased work does not appear.