Update from 8.22 to 8.23 does nothing

Thank you.

You didn't give enough info about your actual problems, if any. Honestly not sure what you are talking about, but it doesn't seem a problem to me except about "does-nothing update" perception?

If so, there are things (update messages, codebase synching, etc.) not always immediately visible unless you run the update process properly.

And any update doesn't guarantee any visible messages or changes, either.

Often times, they are only some under-the-hood changes like triggering asset regenerations cache clearings, or service updates in case aggregations and caches are being enabled so to ensure things are updated.

This update triggers or any empty updates may "do nothing" visibly, but it is not anything to worry about.

However you may want to trace changes using your git tools to see what is going on under the hood only if you are concerned. But IMHO most people hardly care about, except for any regressions or newly covered issues due to updates.

Most reported update errors, if any, are due to failing to follow update SOP.

In short, drush cr drush updb drush cr. Not just drush cr.

Nothing to worry about though if you did update SOP correctly. Be sure to check out Update SOP link at project home for more details.

Yup. Did all the above and admin/reports/updates/update still reports 8.22.

I suppose I could do composer require 'drupal/blazy:^2.23' which would take care of it, but I'd like to figure out what the issue is. I have my host looking into it and will report back... thanks for the quick response!

Unless any server-side issues with composer.lock or permissions, one obvious potential issue is locked versions like so:
composer require drupal/blazy:2.22

Should be generic:
composer require drupal/blazy:^2.0

Note the difference with caret ^ and trailing 0.

Locking is only necessary if any instruction to do so like our previous dev storms after 2.6, so last time locking to 2.5 is the only recommended way to avoid potential errors. Or if you knew for sure the next version is buggier.

But gone were the stormy days since 2.17. You can set up your composer directives like the generic one from now on.

Then on every updates, simply run regular swap command:
composer update -W -n

To update all contrib things once without any more individual composer require + versions which is the point of composer -- simplifying dependency managements. Unless as said a stormy dev warning were published for version locks.

The next 2.24 update SOP covers such potential composer.lock problems under WSOD which might also be applied to your situations after correcting the locked version issue, only if the generic one alone failed:
https://git.drupalcode.org/project/blazy/-/blob/8.x-2.x/docs/UPDATING.md...

First, thank you very much for the quick and detailed response!

I assume that running composer require 'drupal/blazy:^2.23' won't harm any existing configuration data, correct?

If so, I'll then afterwards be able to run composer update drupal/blazy -W -n from here on out, yes? LMK...

Thanks again!

Should be fine.

composer update drupal/blazy -W -n

Should be:

composer update -W -n

Automatically closed - issue fixed for 2 weeks with no activity.