Config Migration

Config Migration

EasyLibrary 3.x is moving from one large config.yml toward split config files.

Supported Split Files

plugin_data/EasyLibrary/config/package-manager.yml
plugin_data/EasyLibrary/config/library-installer.yml
plugin_data/EasyLibrary/config/components.yml
plugin_data/EasyLibrary/config/notifications.yml
plugin_data/EasyLibrary/config/doctor.yml
plugin_data/EasyLibrary/config/logging.yml
plugin_data/EasyLibrary/config/repositories.yml
plugin_data/EasyLibrary/config/modules.yml

If a split file exists, it takes precedence over the matching legacy block in config.yml. If it does not exist, EasyLibrary falls back to config.yml or built-in defaults.

Commands

/easylibrary config doctor
/easylibrary config migrate
/easylibrary config migrate confirm
/easylibrary config repair
/easylibrary config repair confirm
/easylibrary config reload
/easylibrary runtime reload [reload-config|request-runtime-reload|all]

Migration Flow

/easylibrary config doctor
/easylibrary config migrate
/easylibrary config migrate confirm
/easylibrary config doctor

Migration does not delete config.yml.

package-manager, library-installer, notifications, doctor, logging, repositories and modules migrate from config.yml. components migrates from the legacy components.yml file.

Startup update notices are opt-in. notifications.startup.enabled and notifications.startup.update-check must both be true before boot checks query GitHub releases. Manual /easylibrary updates [channel] [refresh] checks can be used any time and write plugin_data/EasyLibrary/update-notices.yml.

Reload Boundary

config reload rereads config files for future EasyLibrary operations. It does not:

• unload packages;
• remount package-backed plugins;
• regenerate PMMP dependency graphs;
• hot-swap loaded PHP code;
• change already loaded permissions.

Restart when changing package loader, runtime autoload, dependencies or proxy state.

Runtime Reload Contract

Use /easylibrary runtime reload reload-config when you want the same bounded config reload through the runtime command surface.

Use /easylibrary runtime reload request-runtime-reload when the desired change is a package-backed provider, proxy, component, command backend, permission, dependency or plugin metadata change. EasyLibrary reports that the request is restart-only instead of pretending PHP/plugin state can be hot-swapped.

Use /easylibrary runtime reload all to reload supported config files now and list the remaining restart boundaries.