Was really surprised (no) to see this issue classified as "support request" and "closed (works as designed)", while Composer command, proposed at release page:
composer update "drupal/core-*" --with-all-dependencies
actually fails, and fails silently, with such an output, that looks perfectly normal:
composer update "drupal/core-*" --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 4 updates, 0 removals
- Upgrading drupal/core-composer-scaffold (10.1.7 => 10.2.0)
- Upgrading drupal/core-project-message (10.1.7 => 10.2.0)
- Upgrading symfony/filesystem (v6.2.7 => v6.4.0)
- Upgrading symfony/finder (v6.2.7 => v6.4.0)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 4 updates, 0 removals
- Downloading drupal/core-composer-scaffold (10.2.0)
- Downloading drupal/core-project-message (10.2.0)
- Downloading symfony/finder (v6.4.0)
- Downloading symfony/filesystem (v6.4.0)
- Upgrading drupal/core-composer-scaffold (10.1.7 => 10.2.0): Extracting archive
- Upgrading drupal/core-project-message (10.1.7 => 10.2.0): Extracting archive
- Upgrading symfony/finder (v6.2.7 => v6.4.0): Extracting archive
- Upgrading symfony/filesystem (v6.2.7 => v6.4.0): Extracting archive
Generating autoload files
44 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories foundYou have to either notice, that too few packages were actually updated, or to go to
admin/reports/updates
page to find out, that upgrade failed.
Obviously many users would never read "Drush versions below 12.4.3 are incompatible with Drupal 10.2.x" statement, placed after "Upgrading from Drupal 6 and 7", and/or would not understand, what should they actually do, which will leave them with half-upgraded sites.