Changelog

NextRush manages releases with Changesets, and changelogs exist at two levels. There is no single hand-maintained "master changelog" beyond the root file below — per-package history lives in each package's own CHANGELOG.md, generated by Changesets at release time.

Root changelog

CHANGELOG.md at the repository root tracks framework-level changes across the core packages — new packages, breaking changes, and cross-cutting fixes (CLI reliability, DI container behavior, the Route Metadata System). This is the best starting point for "what changed recently."

Per-package changelogs

Every publishable package has its own CHANGELOG.md, generated by Changesets from the changeset files merged for each release. These are the authoritative source for a specific package's history — check them when a fix or feature is scoped to one package rather than the whole framework:

packages/<package-name>/CHANGELOG.md

For example: packages/core/CHANGELOG.md, packages/router/CHANGELOG.md, packages/errors/CHANGELOG.md.

Because packages version independently (see the Compatibility Matrix), a package's CHANGELOG.md only reflects releases of that package — it does not track every framework-wide change; cross-cutting changes are recorded in the root changelog instead.

npm release notes

Published versions and their release notes are also visible directly on npm, per package — for example nextrush on npm and @nextrush/core on npm.

GitHub Releases

Tagged releases with notes are published under GitHub Releases.

See also

• Compatibility Matrix — current version of every package.
• Roadmap — what's planned next.