01
Upgrade from a controlled state
Review release notes, pin resolved dependency versions, inspect the lockfile, remove stale dist output, and run the full checks before considering the upgrade complete. On v1.3.3, keep the coordinated package set aligned, including Router, Starter, and SEO; direct local named handlers such as onClick$={increment} are supported while semantic Link navigation remains only an enhancement over independently correct HTML routes.
02
Treat generated output as a release artifact
Manifest, chunks, route HTML, media, sitemap, feeds, and redirects must be generated from the new version and verified as a set.
03
Plan a rollback
Record compatible runtimes, migrations, deprecations, and a rollback point before production rollout. Do not improvise rollback after a public failure.
PRACTICAL LABS
Run this capability.
Each example states the observable output, the boundary that remains your responsibility, and the check that proves the result.
01
Upgrade from a controlled state
Shellpnpm install --frozen-lockfile
pnpm typecheck
pnpm check
pnpm build
git diff --check- OUTPUT
- Dependency resolution, source, generated output, and repository state are checked together.
- BOUNDARY
- Keep rollback artifacts and version notes; do not overwrite a working production deployment blindly.
- PROVE IT
- Record old/new versions, migration steps, output checks, deploy health, and rollback choice.
VERIFICATION
Prove the contract.
Capture version, migration actions, route analysis, checks, release notes, deploy health, and rollback decision in a release report.