Impossible to update an entity revision if the field value you are updating matches the default revision.

FYI, I just faced the same problem using Content Moderation and trying to update the latest draft revision programmatically, but without creating a new revision, so using setSyncing(TRUE). When no additional revision is created, we face the same problem that if the value we try to set is identical to the one stored in the default revision (last published one), then the value is not updated.
Setting $entity->original as suggested in #29 does prevent the issue.

Given this can lead to data loss I think it's time we get this in.

I've opened a follow up ✨ Add loadOriginalEntity function Closed: duplicate to address #20

Bumping to major as per #26

I think 📌 $entity->original doesn't adequately address intentions when saving a revision Needs work already covers #20 so closed the new issue as duplicate of that.

Added credit from #3152820: Workspaces // Revision id in dedicated table not updated on publishing → .

Committed b886bd7 and pushed to 10.1.x. Thanks!

catch → credited matsbla → .

catch → credited amateescu → .

Added a change record: https://www.drupal.org/node/3343661 →

And there's the mentioned 📌 Add a method to access the original property Needs work , my plan for that is to make the replacement for $entity->original behave like the internal workaround here (that also exists in 2-3 other places already), which would then also make that other issue a duplicate.

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

Published the CR