# Updates

How a NextSpark project moves between releases of the `@nextsparkjs` packages.

| Guide | Read it when |
| --- | --- |
| [Upgrading 0.x projects to 0.1.0-beta.192 or later](./06-upgrade-0x-projects.md) | **Start here.** Your project is on a 0.x release (a `contents/themes/<theme>` layout, or a committed `src/app`) and you are moving to beta.192 or later: the single `nextspark migrate` path, what it changes and what to check afterwards. |
| [Core update command](./01-update-core.md) | You are already on beta.192 or later and want to move to another release (`update-core`). |
| [Release a version](./02-release-version.md) | You maintain the framework and publish a release. |
| [0.1.0-beta.192 status](./03-beta-192-status.md) | You want the scope, breaking changes and verification of the beta.192 line (historical). |
| [Root-first contributor migration](./04-beta-192-root-first-contributor-migration.md) | You contribute to the framework repository itself, not to a project built with it. |
| [`sync:app` removal timeline](./05-sync-app-removal.md) | You used `sync:app` or core's postinstall write and need to know what replaces them. |
| [Public API](../22-stability-and-support/05-public-api.md) | Moved to the stability and support section: which `@nextsparkjs/core` subpaths follow SemVer. |