You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm unable to test and upgrade Drupal module dependencies on our project release schedule, because Acquia CMS locks some dependencies down to exact major.minor.patch (X.Y.Z) versions.
Case in point:
Facets 2.0.2 came out but Acquia CMS is still pinned to 2.0.1
Geocoder 8.x-3.28 came out but Acquia CMS is still pinned to 8.x-3.25
Describe the solution you'd like
Instead of pinning to specific point releases, allow projects using acquia_cms to make and test their own updates using ~X.Y.Z which will allow updating the Z but not the X or Y.
This is inline with a change that was just made in Drupal core-recommended as of Drupal 9.5
I'm unable to test and upgrade Drupal module dependencies on our project release schedule, because Acquia CMS locks some dependencies down to exact major.minor.patch (
X.Y.Z
) versions.Case in point:
Describe the solution you'd like
Instead of pinning to specific point releases, allow projects using acquia_cms to make and test their own updates using
~X.Y.Z
which will allow updating theZ
but not theX
orY
.This is inline with a change that was just made in Drupal core-recommended as of Drupal 9.5
https://www.drupal.org/node/3285240
Describe alternatives you've considered
I'm not sure there are any other alternatives besides waiting for an official acquia_cms release where the dependencies are updated.
The text was updated successfully, but these errors were encountered: