Installing a plugin now tells you if it activated, needs a reload, or failed to load.
What's wrong with this entry?
Install and already-installed flows await a reload of the specific plugin id and tailor the confirmation to what actually happened.
- three outcomes: activated, needs /reload-plugins, or a load failure pointing you at /plugin
- the install result carries installedDisabled and installedDisabledByDefault
- a plugin installed in a disabled state is no longer announced as active
The plugin couldn't be loaded
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
Plugin auto-updates can now take effect without a restart
Both mention reload
-
v2.1.239
Skipped-plugin warning no longer overstates what it found
Both mention reload
-
v2.1.242
/reload-plugins now warns about LSP tool changes too
Both mention reload