setSyncing(TRUE) prevents changed timestamp from updating on publish since Drupal 11.1

Summary

Since Drupal 11.1, the changed timestamp is no longer updated when using the "Publish Latest Revision" bulk action. The content is published correctly, but the changed date retains its previous value.

Root cause

In Drupal 11.1.0, the behavior of setSyncing(TRUE) was changed to explicitly preserve the original changed timestamp on save (see Change Record #3250104).

In AdminModeration::publish() (line 167), the code calls:

$this->entity->setSyncing(TRUE);

Prior to Drupal 11.1, this did not prevent the changed field from being automatically updated. Now it does, which means bulk-published content keeps its old changed date.

Affected methods

AdminModeration::publish() — line 167
AdminModeration::unpublish() — line 92 (same issue applies)

Note: AdminModeration::archive() already has setSyncing(TRUE) commented out (line 257), so it is not affected.

Suggested fix

Explicitly set the changed timestamp before saving:

$this->entity->setChangedTime(\Drupal::time()->getRequestTime());

This should be added before the $this->entity->save() call in both publish() and unpublish() methods. This preserves the setSyncing(TRUE) behaviour for other purposes while ensuring the changed date reflects when the action was performed.