Right now, the Entity Reference revision field item creates a new revision from the referenced entity whenever the host entity being saved is a new revision. This is fine in 99% of the situations, but if you migrate content entity revisions, this behaviour creates new revisions from the entities referenced by an entity_reference_revisions field.
Execute the test at #2977853-33: [PP-4] Multifield to Paragraphs migration → .
Check the value of an unmapped (so unsaved) field property, e.g. needs_resave (or skip_new_revision). If it is explicitly set to FALSE (or TRUE), then don't create a new revision.
@tbd
Nothing
@tbd
Nothing.
Needs work
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I am facing same issue with a migration from D7 to D9.5.
@huzooka where did you set value for "needs_resave" ?
Sorry for the laxy PR with no tests, but I need the patch for a project right now. Will try to circle back around when I get a chance with tests.