refactor(plugins): split plugin installation flows#107960
Merged
Merged
Conversation
Contributor
Author
|
Merged via squash.
|
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 15, 2026
* refactor(plugins): split plugin installation flows * fix(plugins): keep compatibility helper private
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Problem This Solves
The plugin installer had grown into a 3,267-line module spanning local packages, npm metadata, managed npm state, rollback, quarantine, and archive flows. That made ownership boundaries difficult to review and forced the file onto the max-lines suppression list.
Why This Change Was Made
Split installation into source- and lifecycle-focused modules while retaining
src/plugins/install.tsas the stable public facade. Runtime behavior, exported APIs, security scanning, audit events, rollback, and managed npm generation semantics remain unchanged.User Impact
No user-visible behavior change. Maintainers get smaller installation modules, clearer dependency direction, and removal of the max-lines suppression.
Evidence
node scripts/run-vitest.mjs src/plugins/install.path.test.ts: 4 passednode scripts/run-vitest.mjs src/plugins/install.test.ts src/plugins/install.npm-spec.test.ts: 165 passedsrc/agents/embedded-agent-runner/**; no installer lint failuresAI-assisted. Maintainer-requested refactor; implementation and proof reviewed before submission.