Conversation
Contributor
Author
|
Follow-up needed in
The Composer version threshold should be confirmed from the published release rather than inferred from the milestone. |
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
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.
Composer resolution currently returns text. Use
composer show --tree --format=jsonand add CLI version detection that preserves prerelease and development suffixes, so callers can choose a parser based on the installed version.Draft pending a Composer release containing composer/composer#13049. That change adds installed versions to child nodes in the JSON tree. Older releases still report only constraints on those nodes, so consumers will need to retain their fallback until the installed Composer version includes the change.