Skip to content

Update Gutenberg Build tool to include the minified CSS #10685

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
youknowriad wants to merge 1 commit into from
+1 −1
Closed

Update Gutenberg Build tool to include the minified CSS #10685

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
"url": "https://develop.svn.wordpress.org/trunk"
},
"gutenberg": {
"ref": "b79bbe25a1b00ce640bfab363f182c678181082f"
"ref": "dea73b609a80016eb1cf3893ea183fe106a06740"
Copy link

@mcsf mcsf Jan 6, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming 4856d5d1842 is used, per Jarda's comment, this LGTM.

Copy link
Contributor Author

@youknowriad youknowriad Jan 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is a branch that is protected and only includes the build changes on top of the previous hash (to avoid bringing any new changes from Gutenberg, let's leave that separate for folks that do the back-porting)

Copy link
Member

@jsnajdr jsnajdr Jan 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for explaining this, I retract my comments now 🙂

Copy link

@mcsf mcsf Jan 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, that makes sense.

Should we come up with some nomenclature for such branches? I suspect it's not the only time we'll push this sort of change, and I don't like the idea of our piling up protected branch names like fix/build-tool-old-hash-do-not-remove-branch in our admin panel with no traceability nor lifetime rules.

},
"engines": {
"node": ">=20.10.0",
Expand Down
Loading