Update plugins

A plugin update first becomes a candidate for review. Open Settings → Plugins, select the plugin and go to Version. The installed revision continues to serve new work until you activate the candidate.

For a folder source, edit and validate the source files, then choose Import from folder again. For another source, use Check this source for an update. A pinned GitHub commit or archive hash identifies fixed contents; to move to a new one, stage the new source from the CLI.

farero plugins update <installation> --source github:<owner>/<repository>@<full-commit>
farero plugins update <installation> --source https://example.com/plugin.tgz --sha256 <archive-sha256>

Update ready to review shows the candidate revision, components and declared data destinations. Check any new command or destination before activation.

Compatible saved settings carry forward. Fields that need a value or no longer accept the old value appear in the candidate form. Save those values before activating. Farero does not silently convert a value to fit a changed type.

Enter any newly declared key in the update review. For a key the installed version already uses, choose Go to beside its name to reach its field under Keys. Review any role override that no longer fits the package requirements. Save or clear unsaved keys before activating. Your installed revision remains selected while you prepare the candidate.

Choose Activate beside the candidate version. New work uses that revision once activation succeeds. Commands and Workflows already using an earlier revision keep it until they finish; Version shows any older revisions still in use.

Your scope choices and pause state stay in place. Updating a paused plugin does not resume it.

After I activate the File summary update, summarize its bundled fixture with label Updated sample and maxLines 2.