-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simplify composer-plugin #5
Simplify composer-plugin #5
Conversation
Signed-off-by: Maximilian Bösing <[email protected]>
Signed-off-by: Maximilian Bösing <[email protected]>
Functionality is the same as before. As I dont think that anyone will ever extend services from composer plugins, I think we can safely create a new major version and let users upgrade. If we are doing this, we could target the composer v2 support to the next major aswell and we are ready for composer v2. If we do not want to do this, I will create the tests based on the composer version in #3 and we are ready for composer v2 aswell. |
For plugins, the only BC break really is if the functionality changes for the end-user consumer of the plugin; the API in this case is how it is consumed, not how it is coded. As such, I think we could likely target a new minor release, as we'd be bumping the Composer and/or PHP requirements only. |
Signed-off-by: Maximilian Bösing <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor nitpick on changelog; otherwise, ready to 🚢
Signed-off-by: Matthew Weier O'Phinney <[email protected]>
Description
Due to the complexity level which is needed to migrate to composer v2 in #3, I would like to propose this simplified version of this plugin.
It does the same as before. Due to the removal of the hole
PackageEvent
stuff, we do not have to create composer version specific unit tests in #3 and so on.What do you think?