Why does one block change update every other block's changedfieldindicator?

[darylknight]

I've just added some field instructions to one of the fields inside our site's main Matrix field. In Project Config, I would expect this to update the project.yaml file with a dateModified, and add the new field instruction to that block's yaml file. Instead, every single block in the matrix field updates it's changedFieldIndicator, which both makes migrations and deployment take longer, and makes it difficult to find what changed in a commit.

It didn't always do this - is this behaviour new?

[brandonkelly]

Craft doesn’t have any changedFieldIndicator properties anywhere, so I’m not sure where that’s coming from or why it would be getting updated.

[darylknight]

Ah, thank you - sorry about that. Yeah, it looks like it's caused by Super Table.