dotCooCoo fd7ff70941 Plug-ins: an update left in the store by a failed put-back turns a disabled plug-in on ...

When plugin.install writes a module that lists permissions, its grant
can't be written, and the old module can't be put back (or, on a first
install, the new module can't be removed), the store holds the new
module. install now takes put_back_plugin's result, so the plug-in's
disabled entries (by id and by stored file) are cleared as for any
install the store holds. The old grant, or none, still doesn't cover the
new module, so the next start skips it until it is approved.

Docs: docs/plugins.md, docs/mcp.md, docs/target-app-parity.md.

2026-11-11 13:03:38 -08:00

..

examples

…

src

Plug-ins: an update left in the store by a failed put-back turns a disabled plug-in on

2026-11-11 13:03:38 -08:00

tests

Merge pull request #6646 from dotCooCoo/fix/plugin-fuzz-fuel-slice

2026-11-12 02:28:28 +07:00

Cargo.toml

Merge main into feat/script-run

2026-11-09 23:43:37 -08:00