Upgrading Janux#

Janux is 0.x, and the version numbers are narrower than semver's "anything may change":

Bump	Means
Minor (`0.5.0` → `0.6.0`)	The breaking bump. Something documented changed; the changelog says what and how to migrate.
Patch (`0.6.0` → `0.6.1`)	Fixes and additions that break nothing documented. Safe to take without reading anything.

New features can ship in a patch — that is deliberate. It keeps the minor meaning exactly one thing: read the changelog before you take this. The full policy, including what can break with how much notice per stability tier, is in VERSIONING.md, and the tier of every export is generated into STABILITY.md from the exports themselves.

The routine#

All @janux/* packages share one version number, so an upgrade is one bump everywhere:

bun update janux @janux/vite @janux/server   # …and the rest you use

Patch jump? Done — nothing to read.
Minor jump? Read the changelog entries between your versions. Every breaking change names its migration.
Run the codemods. For breaks that are mechanical, the release ships the tool that applies them:

janux upgrade --dry-run   # a unified diff of what the jump would change; writes nothing
janux upgrade             # apply it

janux upgrade reads the version your app resolves from node_modules, compares it with the CLI's own, and runs exactly the codemods that fall in that range — each one idempotent and dry-runnable. The catalog and the rules every codemod obeys are in the codemods reference.

Deprecations#

A Stable export gets one full minor of deprecation before removal: the deprecating release keeps the old behavior working and warns at runtime where a warning is possible. Experimental exports can change on any minor with only the changelog as notice — building on one means reading the changelog on every minor.

Coming from another framework?#

This page is about moving between Janux versions. For moving to Janux, see Migrating from Next.js and Migrating from Astro.