Add missing changes to the changelog for the PR #62734

[luisherranz]

What?

Add missing changes to the changelog for the PR #62734

Why?

We forgot to add them in said pull request.

How?

Simply adding them directly to the changelog file in the latest version.

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core.
• Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: luisherranz <luisherranz@git.wordpress.org>
Co-authored-by: SantosGuillamot <santosguillamot@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[SantosGuillamot]

LGTM! 🙂

I can see there is a bug linked from the pull request: Inability to use plain arrays in context.. Should that be included as well?

By the way, just in case it is useful, there is a GitHub workflow to check if a pull request that needs a backport doesn't have it. Maybe a new one to check the Interactivity API changelog when the package files change could prevent this in the future. Not sure if its worth though 😄

[luisherranz]

Maybe a new one to check the Interactivity API changelog when the package files change could prevent this in the future.

I think someone mentioned that it wasn't very useful because not all pull requests need changelog entries.

I can see there is a bug linked from the pull request: Inability to use plain arrays in context.. Should that be included as well?

I don't think it's needed because it's a functionality that should never have been there, although I'm not entirely sure…

[github-actions]

Flaky tests detected in c72b8b7.
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/10389540841
📝 Reported issues:

• [Flaky Test] Create a pattern with overrides #58009 in /test/e2e/specs/editor/various/pattern-overrides.spec.js