Updating Resources

Before updating

1. Record the currently installed resource folder name and version from its manifest or release files.
2. Back up the full resource and any local configuration changes.
3. Read the update notes included with the new version.
4. Compare the old and new configuration files before bringing forward local values.
5. Check whether the release changes dependencies, controls, stored data, or integration behavior.
6. Replace the files using the release's actual update procedure; do not assume an old configuration is drop-in compatible.
7. Restart the resource during an appropriate maintenance period and test its basic controls.
8. If it fails, preserve the logs and restore the previous known-working build.

Release notes

Release notes apply to a specific downloadable build. Each entry covers the version, release date, changes, fixes, configuration changes, dependencies, and known limitations.

A version number shown in the archive filename may differ from text in an older README section. When they disagree, the version in the installed fxmanifest.lua is authoritative.

Configuration migrations

If configuration keys have been added or renamed, manually carry over only applicable values. Avoid copying the entire old file over a new version until the new release's configuration schema has been reviewed. This is particularly relevant for TraumaCore, whose 7.9.5 update instructions call for replacing the full resource and using the included configuration as a basis.