Components: Back-add changelog for TypeScript types

[mirka]

What?

Retroactively adds a changelog entry for #49229.

Why?

I was looking for this information in the changelog and I realized it wasn't in there.

[github-actions]

Flaky tests detected in db249ff.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/5059173855
📝 Reported issues:

• [Flaky Test] should insert elements from multiple completers in a single block #47916 in /test/e2e/specs/editor/various/autocomplete-and-mentions.spec.js

[tyxla]

I recall seeing some comments about this being a breaking change. Should we move it accordingly?

[mirka]

I recall seeing some comments about this being a breaking change. Should we move it accordingly?

I'm assuming we're referring to #50157 (any others?).

That is a good point, though it's kind of tricky because we can't change the semver numbers retroactively 😭 Also I think I would classify this as an enhancement with an unresolved bug, rather than an intentional breaking.

In reality, I'm guessing that it's not that important to warn consumers with a Breaking Change heading here because the disruption would be very apparent to anyone who is relying on a tsc build.

[ciampo]

Also I think I would classify this as an enhancement with an unresolved bug, rather than an intentional breaking.

I also think that this in itself should not be a breaking change. It happened to cause breakage as an unintended consequence

[tyxla]

Sounds good, thank you both for confirming 👍