-
Notifications
You must be signed in to change notification settings - Fork 3
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
Securities are not always updated when those aren't direct dependencies #5
Labels
enhancement
New feature or request
Comments
After thinking about it I conclude that drupal updater must rely on the constraints, otherwise, modules can be calculated automatically. |
After thinking again a good solution would be:
|
This is fixed in #25 . As we always lookup for the direct dependencies, if drupal core has a security, drupal core recommended will be updated. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It happened that the script wasn't able to update the drupal core latest security, when the project has drupal/core-recommended installed.
It looks like as not the complete metapackage has been updated, it is not possible to independently upgrade drupal core.
Steps to reproduce
drupal-updater --security
The text was updated successfully, but these errors were encountered: