Testing: Consolidate CI workflows for changelog testing

[aduth]

What?

• Consolidates check-dataviews-changelog.yml and check-components-changelogs.yml GitHub Actions workflows to a single check-package-changelogs.yml
• Expands new consolidated workflow to cover changes in packages/ui and packages/theme

Related: #78166

Why?

• Code quality: These workflows had largely the same code (evidenced by the changes presenting as a "rename"), and these changes reduce duplication and risk for de-sync
• Performance: Run a single workflow rather than 2+. The job is now checking multiple folders, but this should still be faster than the overhead of additional workflow.
• Coverage: This now includes packages/ui and packages/theme, and could be expanded to include additional packages where we want to have soft enforcement of CHANGELOGs

How?

Consolidate to a single workflow, using GitHub Actions matrix for repeating checks across distinct folders.

Testing Instructions

A temporary change has been included to one of the affected packages to demonstrate CI failure.

Use of AI Tools

Implemented with Claude Code Opus 4.7, with manual review of code differences (via diff) between new and old workflows.

[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: aduth <[email protected]>
Co-authored-by: mirka <[email protected]>
Co-authored-by: desrosj <[email protected]>

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

[aduth]

Expected failure from 4b84f03 works. Including the package name from the matrix in the status message is a nice convenience.

Job logs: https://github.com/WordPress/gutenberg/actions/runs/25675502158/job/75372100030

Run package_path="packages/${PACKAGE}"
Please add a CHANGELOG entry to packages/ui/CHANGELOG.md

This isn't a required check, so if you think your changes are small enough that they don't warrant a CHANGELOG entry, please go ahead and merge without one.
Error: Process completed with exit code 1.

[github-actions]

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

• [Flaky Test] should disable Save draft button during a multi-file gallery upload #77701 in /test/e2e/specs/editor/various/upload-save-lock.spec.js

[desrosj]

This step is pretty large. Is there any way to divide it up into several steps so that they are more atomic/responsible for a single task?

For example, it seems like the relevant_changes check could be it's own step that outputs a 1/0 or true/false value that can be referenced in if: statements for subsequent steps.

[aduth]

Yeah, at least the relevant changes logic being added here could be easy enough to split out on its own as an isolated pre-step. I think the remainder of the logic has a fair bit of shared dependency (e.g. optional_check_notice) that would require a bit more work to split. Although it's probably easy enough to just inline that text vs. sharing a variable, or maybe we don't want the optional-ness at all in which case we can get rid of it 🙂 At the risk of inflating the scope and diff size of this change I'd probably reserve it for a follow-up if we're interested (I'm happy to own that if we want to change course on it being a required check).

[aduth]

This is updated in 5d2b8d8.