# Updates

Update framework and application code and review changed setup templates.

## Review both repositories

Framework and application repositories have independent histories. Check working trees and preserve unrelated changes before updating. Use your established project synchronization and release workflow to incorporate current application records and code.

## Apply an update

Read the changed framework documentation, dependency inputs and setup templates. Update the development checkout first and run focused checks for the behavior your project uses. Rebuild assets when their inputs changed.

`./nimbly system:repair` reports drift from current setup templates. It changes files only with `--yes`; review its report before applying it. Use current core rather than inventing a framework version pin.

## Verify the release

Check the deployed commit and the changed pages or operations on the intended environment. Retain the normal recovery path for your hosting setup. See [deployment](/en/docs/operate/deployment/) and [backup and recovery](/en/docs/operate/backup-recovery/).

## Older application conventions

Use field-level language values for current multilingual resources and active admin paths rather than removed legacy admin routes. Consult the relevant reference when updating older application code; do not publish internal framework implementation details as supported public interfaces.