Managing updates

Once you start from Emberstack, the code is yours. There's no automatic update path, which means you can change anything and you choose what to adopt.

Dependencies

Bun shows what's out of date and updates it:

bun outdated             # what can be updated
bun info astro version   # the latest published version of a package
bun update --latest      # update everything to the latest versions

Update in small batches and check each one:

1. Patch releases first, all together. They're meant to be bug fixes.
2. Minor releases next, one package at a time. Read the release notes for features worth adopting.
3. Major releases last, one at a time. Read the release notes and the migration guide before you update.

After each batch, run bun run build and bunx biome lint ., and try the app with bun run preview before you commit.

EmDash

EmDash has its own upgrader, which updates every EmDash package together and writes a work order:

npx upgrade-emdash@latest

Read .emdash/UPGRADE.md afterwards. It lists each change that affects your version and whether the release adds database migrations. Check migration status before you deploy, as described in The CMS.

Starter improvements

Emberstack keeps improving. You don't need to follow it: if your copy works, keep going. When you want something new, look through the commit history and copy over the changes you need.