Parse required extensions from composer.json
#58
Merged
Conversation
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
Signed-off-by: Maximilian Bösing <[email protected]>
Signed-off-by: Maximilian Bösing <[email protected]>
boesing
force-pushed
the
feature/extensions-parsed-from-composer
branch
from
fb26ca5 to
abeef67
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
With https://github.com/laminas/laminas-continuous-integration-action/releases/tag/1.11.0, only missing extensions are getting "installed" and existing extensions are being enabled (if not already enabled).
Due to this fact, we can parse required PHP extensions from
composer.jsonfor the project.NOTE: This does not use
composer.lockto determine 3rd-party extension requirements ascomposer.lockmay change due tolatestorlowestdependency information!