Every major version that breaks API contracts gets a guide here. Patch and minor versions usually don't need one — read the changelog and follow the standard pull, deploy, watch motion.
Status
No migration guides have been published yet. Check back when the next major version ships, or see the changelog for the most recent breaking changes.
For private/enterprise migrations across very old versions, contact [email protected]. The team has runbooks for migrations off pre-0.9 deployments.
Template for future guides
When a major upgrade ships, the guide on this page follows this shape:
# Migrating from 0.x to 1.x
## Summary
One paragraph: scope of changes, expected downtime, rough effort.
## Breaking changes
| Surface | What changed | What to do |
|---|---|---|
| `/profile/signin` | Returns `{ token, user }` instead of `{ jwt, profile }` | Update SDK to >=1.0 |
| ... | ... | ... |
## Pre-flight
- Snapshot your database
- Pin a maintenance window
- Notify customers
## Steps
<Steps>
<Step>
### Bump the dependency
...
</Step>
<Step>
### Update SDK calls
Specific code diffs.
</Step>
<Step>
### Run the data migration
A script, an admin UI flow, or a managed step.
</Step>
<Step>
### Verify
Smoke tests, what to look for in logs.
</Step>
<Step>
### Roll forward
Deploy. Watch alerts.
</Step>
</Steps>
## Rollback
How to revert if it goes wrong. The cutoff after which rollback is no longer safe.
## Known issues post-upgrade
What to expect that's documented as accepted.
Use this template if you're authoring a migration guide for an internal fork.
Why we don't backport
AppMint backports security fixes to the previous major version. Feature changes are not backported — keep reasonably current.
The supported window is the latest major + the previous major. Older majors are best-effort only; an enterprise contract can extend that window.