Updates
Amazify treats application releases and catalog plugins as separate update channels. Both verify downloaded content before installation.
Application updates
The updater checks the official eripum9/Amazify GitHub repository for the latest eligible final release. Drafts, prereleases, unrelated repositories, and unrecognized assets are not accepted as normal application updates.
Check from the CLI
amazify update check
amazify update installThe install command shows the proposed version and asks for confirmation. It then downloads the expected installer and detached digest, verifies them, and opens the ordinary interactive installer.
Plugin updates
Open the in-app Marketplace to refresh the schema-v2 catalog. Amazify compares each installed manifest version with its catalog entry and shows Update when a newer package exists.
Each plugin update is staged and checked against the catalog's pinned source commit, file sizes, and SHA-256 values before replacing the installed package.
Why the two channels are separate
- Application updates replace Amazify's launcher, daemon, runtime, bridge, and installer-managed files.
- Plugin updates replace only one package under
%APPDATA%\Amazify\plugins. - A plugin can update without requiring a full application reinstall.
- A new Amazify release does not automatically enable downloaded plugins.
If an update is not offered
- Confirm you can reach GitHub over HTTPS.
- Check that the release is final rather than a draft or prerelease.
- Run
amazify --versionand compare it with the release page. - For a plugin, reopen Marketplace and compare its installed manifest version.
- Review
%APPDATA%\Amazify\logsfor a bounded download, redirect, digest, or catalog validation error.
Manual fallback
You can always download the latest installer directly from the official release page and run it over the current installation.