feat: update plugin-code-execution to version 0.0.4 and change mode t… #28
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.
This pull request updates the code execution plugin and its dependencies to use a standardized execution mode identifier. The main change is the replacement of the previously used custom string
"custom"with the new explicit mode"code_execution"throughout the plugin, examples, documentation, and tests. Additionally, the plugin and core package versions are bumped to reflect these changes.Standardization of execution mode:
Replaced all instances of
mode: "custom"withmode: "code_execution"in the plugin application logic (plugin.ts), examples (examples/basic-usage.ts), documentation (README.md), and tests (code_execution.test.ts). This ensures consistent identification and usage of the code execution mode across the codebase. [1] [2] [3] [4] [5] [6]Updated the
ExecutionModetype definition intypes.tsto allow any string value, removing the special"custom"literal and supporting future extensibility.Version updates:
@mcpc/corepackage from0.3.4to0.3.5in both its own manifest and as a dependency in the plugin. [1] [2]@mcpc/plugin-code-executionpackage from0.0.3to0.0.4.