Forward compatibility for composer v2.3.6+ #51
Merged
Conversation
This file contains 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 <2189546+boesing@users.noreply.github.com>
|
Would it make sense to declare |
I was thinking about this as well. But since I know that in CI pipelines (even in ours) are not always the latest and greatest composer versions, this might be kinda annoying for some projects. WDYT? |
|
Works for me - dependency requirement can be bumped later. |
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
To avoid deprecation messages with composer v2.3.6 and above, we follow the deprecation messages suggestion and use
RepositoryFactory#defaultReposWithDefaultManagerinstead ofRepositoryFactory#defaultRepos.fixes #47