Only update project packages as much as necessary? #12341
-
|
As a Drupal developer I have done some pretty juicy major version upgrades. The way I prefer to approach major version upgrades is understanding which Drupal core version I want to upgrade to, and only upgrade or downgrade everything else (relative to their currently locked versions) as much as needed so it is compatible with the new core version. In other words, give me the version of Drupal core that I want and then minimally change what is necessary to be compatible with the new core version. For example: composer.json {
"require": {
"drupal/core": "^10",
"drupal/module-a": "^2.1"
"drupal/module-b": "^4"
}
}composer.lock (for the listed composer.json packages): {
"require": {
"drupal/core": "10.2.1",
"drupal/module-a": "2.2"
"drupal/module-b": "4.3"
}
}Given the following:
So what I'd like to do is give an update command that says "upgrade drupal/core to 11.1.4, and upgrade or downgrade everything else only as much as necessary (relative to a package's currently locked version)". So, the constraint effectively becomes:
Assume preferring stable and minimum stability of dev. So, say some command exists to accomplish this, the result of that command should result in new installed versions:
I thought Is there a singular command that works here? Are there any modifications you would make to |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 11 replies
-
|
the behavior of |
Beta Was this translation helpful? Give feedback.
-
|
As I said before, once a package cannot be preserved at its existing version by
|
Beta Was this translation helpful? Give feedback.
-
|
@stof apologies for not grokking sooner. So the idea is that when a package is no longer able to remain at the exact same version, then the normal procedure for matching the latest version possible within constraints is used? So really what I'm imagining is something like EDIT: If it is true that once a version cannot remain the same given the constraints, I think the documentation of the
...in particular With that clarifying language for the minimal changes feature I would have understood things much more clearly. |
Beta Was this translation helpful? Give feedback.
-
|
The documentation of Composer is open-source (in this repo). Feel free to send a PR to improve it. Regarding your proposed |
Beta Was this translation helpful? Give feedback.
-
Good point, I will consider this.
Understood this is complex, I guess I was just imagining if there was an option available to accommodate this need then it might be an appropriate name for that. I think the process I've outlined above, combining I'll mark this as answered. Thanks @stof this has been a good back and forth conversation, appreciate your time. |
Beta Was this translation helpful? Give feedback.
-
|
If you want to prevent downgrades, maybe starting with |
Beta Was this translation helpful? Give feedback.
-
|
#12349 allows --minimal-changes for full updates, and hopefully clarifies docs a little bit too. Please take a look. I'm not sure I'd want to do more than that as updating to the least deviation i.e. updating but to something that's still outdated seems kinda silly and not worth the implementation effort to me. |
Beta Was this translation helpful? Give feedback.
Good point, I will consider this.
Understood this is complex, I guess I was just imagining if there was an option available to accommodate this need then it might be an appropriate name for that. I think the process I've outlined above, combining
--minimal-changesand--prefer-lowestgets me to where I need to go for now.I'll mark this as answered. Thanks @stof this has been a good back and forth conversation, appreciate your time.