Changelog: Add missing label-to-feature mappings#76646
Merged
Conversation
Add mappings for labels that were causing PRs to appear uncategorized in the generated changelog: - `[Tool] ESLint plugin` → Tools - `[Package] DataViews` → DataViews - `[Package] Core Data` → Data Layer - `Connectors screen` → Connectors - `[Package] UI` → Components - `[Package] Compose` → Components - `[Package] Theme` → Components - `Design System` → Components
aduth
approved these changes
Mar 18, 2026
Member
aduth
left a comment
aduth
left a comment
There was a problem hiding this comment.
Makes sense 👍
Separately, this raises a couple thoughts:
- I wonder how we can proactively address these issues in the future. This feels similar to the type of problem I'm trying to address in #76263, for example.
- On labeling conventions, "Connectors screen" doesn't feel entirely consistent. Is it a feature (i.e. should have "[Feature]" prefix)? It doesn't feel broad enough to be unscoped like others which are unscoped.
| '[Package] E2E Tests': 'Testing', | ||
| '[Package] E2E Test Utils': 'Testing', | ||
| '[Type] Automated Testing': 'Testing', | ||
| 'Connectors screen': 'Connectors', |
Member
There was a problem hiding this comment.
This is the only "new" category, as I understand. We don't have to do anything special to make that work properly, do we?
Contributor
Author
There was a problem hiding this comment.
For generating the changelog there's nothing more we need to do - it really is just that simple.
Point taken about the label name not being scoped properly though. @jorgefilipecosta / @gziolo should the Connectors screen label be renamed to [Feature] Connectors screen ?
|
Size Change: 0 B Total Size: 8.76 MB ℹ️ View Unchanged
|
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Flaky tests detected in d0c5743. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/23263259407
|
Contributor
Author
It's been a few days without an answer, so I've merged. @jorgefilipecosta / @gziolo if you decide to rename the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Adds missing label-to-feature mappings in the changelog generation script so PRs are correctly categorized.
Why?
During the Gutenberg 22.8 release, many PRs appeared uncategorized in the generated changelog because their GitHub labels weren't mapped to changelog sub-headings. This was especially noticeable for Connectors, DataViews, Core Data, UI, Compose, and Theme/Design System PRs.
How?
Added entries to
LABEL_FEATURE_MAPPINGinbin/plugin/commands/changelog.js:[Tool] ESLint plugin→ Tools (type mapping)[Package] DataViews→ DataViews[Package] Core Data→ Data LayerConnectors screen→ Connectors[Package] UI→ Components[Package] Compose→ Components[Package] Theme→ ComponentsDesign System→ ComponentsTesting Instructions
npm run other:changelog -- --milestone="Gutenberg 22.8"Use of AI Tools
Claude Code was used to assist with identifying uncategorized PRs, recommending label mappings, and drafting this PR.