- It doesn't recognise the 2-dash arguments
$ ddev drupal-updater --all --with-core --commit-steps
WARN: Unknown option --
WARN: Unknown option -l
WARN: Unknown option -l
WARN: Unknown option --
WARN: Unknown option -w
WARN: Unknown option -t
WARN: Unknown option -h
WARN: Unknown option --
WARN: Unknown option -r
WARN: Unknown option -e
WARN: Unknown option --
WARN: Unknown option -m
WARN: Unknown option -m
WARN: Unknown option -t
WARN: Unknown option --
WARN: Unknown option -t
WARN: Unknown option -e
WARN: Unknown option -p
- It should output the help when using no arguments instead of the below
$ ddev drupal-updater
Creating database snapshot xxxx_20260702145026
Created database snapshot xxxx_20260702145026
Restore this snapshot with 'ddev snapshot restore xxxx_20260702145026'
No update needed for . The version is already .
- It does not run the update hooks after every module update
- It should respect the version constraints set in
composer.json or add an argument to change them
example:
command ddev drupal-updater -a -g -c
"drupal/core-recommended": "~11.3.13" went to "drupal/core-recommended": "~11.4.0" while it should go to 11.3.14 (in case we're going from .13 to .14)
composer.jsonor add an argument to change themexample:
command
ddev drupal-updater -a -g -c"drupal/core-recommended": "~11.3.13"went to"drupal/core-recommended": "~11.4.0"while it should go to11.3.14(in case we're going from .13 to .14)