Skip to content
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

Adding Notes about Composer Version Constraints. #423

Closed
wants to merge 3 commits into from
Closed

Adding Notes about Composer Version Constraints. #423

wants to merge 3 commits into from

Conversation

jonpugh
Copy link

@jonpugh jonpugh commented Sep 5, 2018

This explains that to upgrade drupal with the composer update command you have to change the drupal/core version constraint.

This explains that to upgrade drupal with the `composer update` command you have to change the `drupal/core` version constraint.
@jonpugh
Copy link
Author

jonpugh commented Sep 5, 2018

Maybe we should suggest the wildcard version constraint, it's a little easier to understand I think...

If you use ~8.4 it could be 8.5, 8.6, etc.
If you use 8.* it could also be 8.5, 8.6, etc, but you don't see the older version and wonder why.

Seems more intuitive.

@hansfn
Copy link
Contributor

hansfn commented Sep 7, 2018

I'm fine with either version constraint. However, we might not need all this general info as the default for new install is the caret notation ("^8.6.0") which always all minor updates. In the Drupal.org docs I just wrote:

If you are upgrading from 8.5 to 8.6, you need to replace "~8.5.x" with "^8.6.0" for drupal/core and webflo/drupal-core-require-dev in composer.json

That line can eventually be removed ...

@AlexSkrypnyk
Copy link
Collaborator

This pull request/issue has been inactive for over a year and is being closed due to inactivity. If the issue still persists or the contribution is still relevant, please feel free to reopen it or create a new one.

Thank you for your understanding and your contributions to the project!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants