Remove mu-plugin as package type - #242
Merged
Merged
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request removes support for the mu-plugin (must-use plugin) package type across the entire codebase, including CLI commands, installer logic, validation rules, JSON schema, and documentation. Only theme and plugin remain as valid package types. There are no review comments, and I have no additional feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
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.
This PR removes
mu-pluginas a supported package type for security reasons.Since must-use plugins are loaded directly by WordPress, allowing downloaded packages to be installed as
mu-plugincreates a risk that untrusted code could be executed automatically at runtime. The potential impact of that risk is significant enough that we should not support this workflow.There is also a usability concern. WordPress only loads PHP files placed directly in the
mu-pluginsdirectory. It does not automatically load plugins stored in subdirectories, which can lead to confusion when a package is installed but never loaded. Supporting directory-basedmu-pluginpackages would require an additional custom loader.Users who want to deploy a plugin as a must-use plugin can still do so by using lifecycle scripts to move or copy the plugin into the desired location after installation.