Skip to content

Limit wp-build esbuild concurrency - #79889

Merged
sirreal merged 9 commits into
trunkfrom
codex/wp-build-concurrency-limit
Oct 22, 2026
Merged

sirreal merged 9 commits into
trunkfrom
codex/wp-build-concurrency-limit

Conversation

@louwie17

@louwie17 louwie17 commented Jul 6, 2026 •

Copy link
Copy Markdown
Contributor

What?

Adds a global concurrency limit for @wordpress/build esbuild jobs.

  • Adds a shared buildWithConcurrency() wrapper for all esbuild.build() calls in wp-build.
  • Limits concurrency to half of os.availableParallelism(), rounded up.
  • Prints the selected concurrency at build start.
  • Documents the limit and adds focused unit coverage for the default calculation and queueing.

Fixes #79888.

Why?

wp-build currently schedules package, route, widget, style, and worker esbuild jobs without a global cap. Large projects can start many bundles at once, which oversubscribes CPU and memory. In downstream projects with many widgets this can make builds slower and can OOM CI runners.

Local Gutenberg build:all benchmark

I re-tested this PR locally on July 6, 2026 with npm run build, using the same checkout and machine for both runs. Node reported 12 available CPUs, so this PR used a concurrency of 6, the same as the current half-CPU default.

Run Commit npm run build total wp-build portion Wall time via /usr/bin/time -p
Test 1 - Before, trunk 153f003c3fd 38s 27,092ms -
Test 1 - After, this PR cc6804713d4 29s 20,978ms -
Test 2 - Before, trunk 153f003c3fd 32s 23,546ms 32.46s
Test 2 - After, this PR cc6804713d4 29s 20,460ms 29.44s

The first run was a fresh build and showed the larger difference; the second was warm, which accounts for the smaller gap.

Jetpack CI results

Tested in Jetpack CI with a pnpm override of @wordpress/build: Automattic/jetpack#53394 (this PR) against Automattic/jetpack#53393 (its merge base). This PR lowered peak memory during wp-build in every round, mostly because far fewer Sass compiler processes ran at once, and build time did not change measurably. See the comment below for the setup, per-run links and detailed numbers.

Testing Instructions

  1. Run npm install if dependencies are not already installed.
  2. Run npm run test:unit -- packages/wp-build/lib/test/build-concurrency.js.
  3. Run npm run build and confirm the output includes Using build concurrency: <n>, where <n> is half of your available CPUs, rounded up.

Testing performed

  • npm run build on trunk (153f003c3fd) and on this PR (cc6804713d4) for the benchmark above
  • npm run test:unit -- packages/wp-build/lib/test/build-concurrency.js
  • npm run lint:js -- packages/wp-build/lib (no errors)
  • npm run typecheck -- packages/wp-build/tsconfig.json
  • node tools/validation/validate-changelogs.ts --require-pr=79889 packages/wp-build/CHANGELOG.md

🤖 Generated with Claude Code

https://claude.ai/code/session_01UHkHDHxL2zAvGw9N8FMrHz

@louwie17
louwie17 force-pushed the codex/wp-build-concurrency-limit branch from deaf89e to fe78504 Compare July 6, 2026 09:23
@github-actions

github-actions Bot commented Jul 6, 2026 •

Copy link
Copy Markdown

Size Change: 0 B

Total Size: 7.81 MB

compressed-size-action

@louwie17
louwie17 force-pushed the codex/wp-build-concurrency-limit branch 2 times, most recently from 20b09fa to cc68047 Compare July 6, 2026 10:53
@github-actions

github-actions Bot commented Jul 6, 2026 •

Copy link
Copy Markdown

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

@louwie17
louwie17 marked this pull request as ready for review July 6, 2026 12:12
@louwie17
louwie17 requested a review from desrosj as a code owner July 6, 2026 12:12
@louwie17 louwie17 added [Package] wp-build /packages/wp-build [Type] Enhancement A suggestion for improvement. labels Jul 6, 2026

@Nikschavan Nikschavan left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This tested well for me, Thank you!

Comment thread packages/wp-build/README.md Outdated
### Build Concurrency

By default, `wp-build` limits concurrent `esbuild` build jobs to half of the
available CPU parallelism, clamped between 2 and 8 jobs. This prevents large

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

MAX_DEFAULT_BUILD_CONCURRENCY on the top is defined 18, so I imagine the clamped concurrency is between 2 and 16?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Aaah this should be updated.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Updated: #79889

@louwie17 louwie17 changed the title [codex] Limit wp-build esbuild concurrency Limit wp-build esbuild concurrency Jul 6, 2026
@aduth

aduth commented Jul 6, 2026

Copy link
Copy Markdown
Member

It may be a few days before I have a chance to look at this deeply, but I agree with the general premise of what this is proposing, and that unlimited concurrency would likely produce worse outcomes for a project the scale of Gutenberg and others.

On the specific approach, I know that @wordpress/build has been built to be rather opinionated by default, so I'm not sure if this should even be configurable or if the revised default is sufficient. We could always add configurability later.

As a broader point, I still think spawning a bunch of individual ESBuild processes is likely always going to be less efficient than using their Entry points feature, but last I looked this was rather complicated by the various bespoke customizations we've introduced in the build, and this has likely only gotten even more complex over time.

@louwie17

louwie17 commented Jul 7, 2026

Copy link
Copy Markdown
Contributor Author

On the specific approach, I know that @wordpress/build has been built to be rather opinionated by default, so I'm not sure if this should even be configurable or if the revised default is sufficient. We could always add configurability later.

I be happy to remove the configuration part! If I do remove this, I wonder if we should change the logic? ( or not ). It kind of looked like that using half of the available CPU's seemed optimal. But that is partly for a local machine, I bet this wouldn't be as accurate for CLI.
Having said that, we could keep the env variable option only.

As a broader point, I still think spawning a bunch of individual ESBuild processes is likely always going to be less efficient than using their Entry points feature, but last I looked this was rather complicated by the various bespoke customizations we've introduced in the build, and this has likely only gotten even more complex over time.

I didn't specifically look into this, mostly because we were already spinning up different ESBuild processes for each. I am happy to explore, but this may also be a good follow up?

@louwie17
louwie17 force-pushed the codex/wp-build-concurrency-limit branch from 75c30e0 to 5026013 Compare July 7, 2026 12:55
@aduth

aduth commented Jul 10, 2026

Copy link
Copy Markdown
Member

I be happy to remove the configuration part! If I do remove this, I wonder if we should change the logic? ( or not ). It kind of looked like that using half of the available CPU's seemed optimal. But that is partly for a local machine, I bet this wouldn't be as accurate for CLI.

Assuming you mean CI, and if we're not going to tinker that as part of this PR, then we can always add the feature later when we decide it's a problem that we want to tackle.

My hunch is that if we settle to a fixed value, and maybe even use a library like p-queue (or its sindre family peers p-limit or p-all), this whole thing could be pretty simple improvement over the current behavior.

I didn't specifically look into this, mostly because we were already spinning up different ESBuild processes for each. I am happy to explore, but this may also be a good follow up?

Yeah, definitely not suggesting it as a blocker for this improvement. Though it's a can we've continued to kick down the road for a while now 😅

@aduth

aduth commented Jul 10, 2026 •

Copy link
Copy Markdown
Member

I haven't looked, but worth comparing the CI timings impact on this branch vs. a control like trunk.

@louwie17

Copy link
Copy Markdown
Contributor Author

Assuming you mean CI, and if we're not going to tinker that as part of this PR, then we can always add the feature later when we decide it's a problem that we want to tackle.

Oops yeah, I meant CI.

My hunch is that if we settle to a fixed value, and maybe even use a library like p-queue (or its sindre family peers p-limit or p-all), this whole thing could be pretty simple improvement over the current behavior.

I didn't explore any libraries for this, given the actual changes where not that big. But happy to explore.

@louwie17
louwie17 force-pushed the codex/wp-build-concurrency-limit branch from 5026013 to 0c50f37 Compare July 14, 2026 14:18
@louwie17

Copy link
Copy Markdown
Contributor Author

I haven't looked, but worth comparing the CI timings impact on this branch vs. a control like trunk.

On CI weirdly enough I haven't noticed a big difference, and I wondered if that has to do with the CPU its running on and if it even supports concurrency ( I get a feeling it doesn't, or it did have to be configured differently ):
CI trunk:
Screenshot 2026-07-14 at 16 25 40

CI concurrency limit:
Screenshot 2026-07-14 at 16 25 35

@aduth

aduth commented Jul 31, 2026

Copy link
Copy Markdown
Member

I think this work is valuable and I'd like to see it continued. I think we need some more measurement and tuning. I also find it curious that there's no CI improvement. I see you temporarily overrode the concurrency in 1464560 to 4, but it's not clear if the timings made a difference there? I'm also not clear on the specifics around "warm" builds mentioned in the original comment, because there is no inherent caching to the build.

It does seem like the benefit will largely be for development machines with many cores that can maximize the parallelism, but I'd be curious to try to see what the exact effect is with different values and over more runs. Should we be using the full number of cpus rather than half, for example.

@louwie17 let me know if I can help try some of this tuning.

@manzoorwanijk manzoorwanijk left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

The speedup does not reproduce

My first (naive) pass ran 3x baseline then 3x PR, and reproduced the PR's result almost exactly: ~20.2s baseline vs ~16.9s PR, a 16% win. That was an artifact. Load average on this machine was 61 (Chrome), so sequential blocks drift.

Re-running interleaved, alternating baseline and PR within each round so drift cancels:

Round base (uncapped) PR default (9) PR --concurrency=4
1 21739 ms 20019 ms 20227 ms
2 20291 ms 20837 ms 20279 ms
3 19305 ms 19186 ms 20089 ms
4 19739 ms 19318 ms 19562 ms
5 19167 ms 20096 ms 19961 ms
median 19739 ms 20019 ms 20089 ms

Flat. The within-condition spread (~2.5s) is larger than any between-condition difference.

Comment on lines +28 to +30
return typeof os.availableParallelism === 'function'
? os.availableParallelism()
: os.cpus().length;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This is available since Node 18, and thus we don't need this typeof check.

louwie17 and others added 8 commits October 22, 2026 11:54
The typeof guard and os.cpus() fallback were only needed for Node < 18.14.
wp-build requires Node >= 20.10, so os.availableParallelism() is always
available.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QWvvMSSnAkdVhFL4JBRf67
Use the full available CPU parallelism as the default instead of half,
still clamped between 2 and 16.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QWvvMSSnAkdVhFL4JBRf67
Trunk moved unit tests from Jest to Vitest: import the Vitest APIs
explicitly, mock with `vi`, and assert the warning with `toHaveWarnedWith`
so the console guard accepts it. Drop the dependency group comments that
trunk no longer uses.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011b5CpdkcW8GMR9s57P1wsr
Use half of `os.availableParallelism()` (at least one) as the build
concurrency, and drop the `--concurrency` flag and `WP_BUILD_CONCURRENCY`
environment variable overrides. Move the changelog entry under
`## Unreleased`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UHkHDHxL2zAvGw9N8FMrHz
@louwie17
louwie17 force-pushed the codex/wp-build-concurrency-limit branch from f0b9c33 to 22fc93e Compare October 22, 2026 09:55

@sirreal sirreal left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This looks good, thank you.

I believe the printed item timings weren't representative before (everything competing in parallel) and they're likely worse now (adds wait time as well) but that's a minor detail.

Thank you, this will be helpful.

@sirreal

sirreal commented Oct 22, 2026

Copy link
Copy Markdown
Member

I think the configuration may be helpful, especially with environment variables that can be configured on CI, but I agree on adding it later if there's need.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UHkHDHxL2zAvGw9N8FMrHz
@sirreal
sirreal enabled auto-merge (squash) October 22, 2026 10:34
@sirreal
sirreal merged commit 0f962ac into trunk Oct 22, 2026
88 of 89 checks passed
@sirreal
sirreal deleted the codex/wp-build-concurrency-limit branch October 22, 2026 11:00
@github-actions github-actions Bot added this to the Gutenberg 24.4 milestone Oct 22, 2026
@desrosj desrosj added the Backport to WP 7.2 Beta/RC Pull request that needs to be backported to the WordPress major release that's currently in beta label Oct 27, 2026
@github-actions github-actions Bot removed the Backport to WP 7.2 Beta/RC Pull request that needs to be backported to the WordPress major release that's currently in beta label Oct 27, 2026
gutenbergplugin pushed a commit that referenced this pull request Oct 27, 2026
wp-build started every esbuild build at once. Running them all
together used far more memory without making the build faster, and
large builds often ran out of memory.

Queue the builds and run at most half the available CPU cores' worth
at a time, rounded up.

---------

Co-authored-by: louwie17 <louwie17@git.wordpress.org>
Co-authored-by: Nikschavan <nikschavan@git.wordpress.org>
Co-authored-by: manzoorwanijk <manzoorwanijk@git.wordpress.org>
Co-authored-by: sirreal <jonsurrell@git.wordpress.org>
Co-authored-by: aduth <aduth@git.wordpress.org>
Co-authored-by: retrofox <retrofox@git.wordpress.org>
Co-authored-by: simison <simison@git.wordpress.org>
@github-actions github-actions Bot added the Backported to WP Core Pull request that has been successfully merged into WP Core label Oct 27, 2026
@github-actions

Copy link
Copy Markdown

I just cherry-picked this PR to the wp/7.2 branch to get it included in the next release: 67cbadb

wporg-sync pushed a commit to WordPress/wordpress-develop that referenced this pull request Oct 27, 2026
This updates the pinned commit hash of the Gutenberg repository from `be6a50be6834e922b9db12c75c9a2cd817b2db59` to `d72020a651eda64dcc53b5dbd5b9d5bd511c4cc9` (version 24.3.0-rc.1).

A full list of changes included in this commit can be found on GitHub: WordPress/gutenberg@be6a50b...d72020a

- BorderControl: Remove double focus outline (WordPress/gutenberg#85173)
- Snackbar: Use design system focus ring (WordPress/gutenberg#85168)
- SelectControl: Fix default options showing the `Select` placeholder (WordPress/gutenberg#85172)
- Actions API: Remove the unsupported `single` action context (WordPress/gutenberg#85186)
- Client-side media: Upgrade wasm-vips to 0.0.19 and raise memory budgets accordingly (WordPress/gutenberg#84980)
- Styles: Fix inconsistent 'Elements' tools panel heading level (WordPress/gutenberg#85247)
- `media-utils`/MediaEdit: use design system focus ring (WordPress/gutenberg#84940)
- Icons: Add new form based icons. (WordPress/gutenberg#84074) (WordPress/gutenberg#85360)
- Navigation: keep custom CSS off inner list containers (WordPress/gutenberg#84881) (WordPress/gutenberg#85367)
- Navigation: keep Global Styles custom CSS off inner list containers (WordPress/gutenberg#85366)
- Edit as HTML: Show design system focus ring on the HTML textarea (WordPress/gutenberg#85266) (WordPress/gutenberg#85359)
- Icons: Restore the missing speech bubble in postComments (WordPress/gutenberg#85275)
- Block Directory: Standardize downloadable block focus indicators (WordPress/gutenberg#85307)
- Global Styles: Add icons and tweak styling for element and block buttons (WordPress/gutenberg#85363) (WordPress/gutenberg#85414)
- Tests: Stop asserting Core lacks the core fields functions (WordPress/gutenberg#85201)
- Meta Boxes: Use the design system focus ring for the panel toggle (WordPress/gutenberg#85355) (WordPress/gutenberg#85410)
- DataViews: Use the design system focus ring for list items. (WordPress/gutenberg#85358) (WordPress/gutenberg#85435)
- Components: Standardize checkbox and radio focus outlines (WordPress/gutenberg#85379) (WordPress/gutenberg#85436)
- UI: Use solid brand highlights for popup items (WordPress/gutenberg#84087)
- Media: Preserve EXIF metadata when converting HEIC to JPEG client-side (WordPress/gutenberg#82040)
- Icons: Add error, info and postComments to the core-admin collection (WordPress/gutenberg#85452)
- UnitControl: Use the design system outline for the unit select focus ring (WordPress/gutenberg#85444)
- Page List: Keep pages visible in the Navigation sidebar in contentOnly (WordPress/gutenberg#85357)
- Icons: Add new asterisk icon (WordPress/gutenberg#85442) (WordPress/gutenberg#85498)
- wp-env: Keep Debian security updates in Bullseye-based images (WordPress/gutenberg#85469)
- Editor: Guard entity preload filters and share entity actions/fields logic (WordPress/gutenberg#85390) (WordPress/gutenberg#85499)
- UI: Scale Spinner stroke width with its size (WordPress/gutenberg#85378)
- [WP 7.2] Fix the block-library TypeScript test project (WordPress/gutenberg#85533)
- Editor: Vertically center the Categories loading spinner (WordPress/gutenberg#85563)
- DataViews: Render table bulk actions outside the table (WordPress/gutenberg#85250) (WordPress/gutenberg#85571)
- Record e2e traces only when a failed test is retried (WordPress/gutenberg#85428)
- Writing flow: fix triple click in a list item selecting the next item (WordPress/gutenberg#85569)
- Build: Limit concurrent wp-build builds (WordPress/gutenberg#79889)
- Icons: Promote Dashicon replacements to `core-admin` and map their Dashicons (WordPress/gutenberg#85541)
  
Props peterwilsoncc, mamaduka.
See #66340

git-svn-id: https://develop.svn.wordpress.org/trunk@64796 602fd350-edb4-49c9-b593-d223f7449a82
wporg-sync pushed a commit to WordPress/WordPress that referenced this pull request Oct 27, 2026
This updates the pinned commit hash of the Gutenberg repository from `be6a50be6834e922b9db12c75c9a2cd817b2db59` to `d72020a651eda64dcc53b5dbd5b9d5bd511c4cc9` (version 24.3.0-rc.1).

A full list of changes included in this commit can be found on GitHub: WordPress/gutenberg@be6a50b...d72020a

- BorderControl: Remove double focus outline (WordPress/gutenberg#85173)
- Snackbar: Use design system focus ring (WordPress/gutenberg#85168)
- SelectControl: Fix default options showing the `Select` placeholder (WordPress/gutenberg#85172)
- Actions API: Remove the unsupported `single` action context (WordPress/gutenberg#85186)
- Client-side media: Upgrade wasm-vips to 0.0.19 and raise memory budgets accordingly (WordPress/gutenberg#84980)
- Styles: Fix inconsistent 'Elements' tools panel heading level (WordPress/gutenberg#85247)
- `media-utils`/MediaEdit: use design system focus ring (WordPress/gutenberg#84940)
- Icons: Add new form based icons. (WordPress/gutenberg#84074) (WordPress/gutenberg#85360)
- Navigation: keep custom CSS off inner list containers (WordPress/gutenberg#84881) (WordPress/gutenberg#85367)
- Navigation: keep Global Styles custom CSS off inner list containers (WordPress/gutenberg#85366)
- Edit as HTML: Show design system focus ring on the HTML textarea (WordPress/gutenberg#85266) (WordPress/gutenberg#85359)
- Icons: Restore the missing speech bubble in postComments (WordPress/gutenberg#85275)
- Block Directory: Standardize downloadable block focus indicators (WordPress/gutenberg#85307)
- Global Styles: Add icons and tweak styling for element and block buttons (WordPress/gutenberg#85363) (WordPress/gutenberg#85414)
- Tests: Stop asserting Core lacks the core fields functions (WordPress/gutenberg#85201)
- Meta Boxes: Use the design system focus ring for the panel toggle (WordPress/gutenberg#85355) (WordPress/gutenberg#85410)
- DataViews: Use the design system focus ring for list items. (WordPress/gutenberg#85358) (WordPress/gutenberg#85435)
- Components: Standardize checkbox and radio focus outlines (WordPress/gutenberg#85379) (WordPress/gutenberg#85436)
- UI: Use solid brand highlights for popup items (WordPress/gutenberg#84087)
- Media: Preserve EXIF metadata when converting HEIC to JPEG client-side (WordPress/gutenberg#82040)
- Icons: Add error, info and postComments to the core-admin collection (WordPress/gutenberg#85452)
- UnitControl: Use the design system outline for the unit select focus ring (WordPress/gutenberg#85444)
- Page List: Keep pages visible in the Navigation sidebar in contentOnly (WordPress/gutenberg#85357)
- Icons: Add new asterisk icon (WordPress/gutenberg#85442) (WordPress/gutenberg#85498)
- wp-env: Keep Debian security updates in Bullseye-based images (WordPress/gutenberg#85469)
- Editor: Guard entity preload filters and share entity actions/fields logic (WordPress/gutenberg#85390) (WordPress/gutenberg#85499)
- UI: Scale Spinner stroke width with its size (WordPress/gutenberg#85378)
- [WP 7.2] Fix the block-library TypeScript test project (WordPress/gutenberg#85533)
- Editor: Vertically center the Categories loading spinner (WordPress/gutenberg#85563)
- DataViews: Render table bulk actions outside the table (WordPress/gutenberg#85250) (WordPress/gutenberg#85571)
- Record e2e traces only when a failed test is retried (WordPress/gutenberg#85428)
- Writing flow: fix triple click in a list item selecting the next item (WordPress/gutenberg#85569)
- Build: Limit concurrent wp-build builds (WordPress/gutenberg#79889)
- Icons: Promote Dashicon replacements to `core-admin` and map their Dashicons (WordPress/gutenberg#85541)
  
Props peterwilsoncc, mamaduka.
See #66340
Built from https://develop.svn.wordpress.org/trunk@64796


git-svn-id: http://core.svn.wordpress.org/trunk@63946 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@simison

simison commented Nov 16, 2026

Copy link
Copy Markdown
Member

I noticed we have a PR to add config, in case anyone in this thread find a need for it:

arshidkv12 pushed a commit to arshidkv12/wordpress-develop that referenced this pull request Nov 21, 2026
This updates the pinned commit hash of the Gutenberg repository from `be6a50be6834e922b9db12c75c9a2cd817b2db59` to `d72020a651eda64dcc53b5dbd5b9d5bd511c4cc9` (version 24.3.0-rc.1).

A full list of changes included in this commit can be found on GitHub: WordPress/gutenberg@be6a50b...d72020a

- BorderControl: Remove double focus outline (WordPress/gutenberg#85173)
- Snackbar: Use design system focus ring (WordPress/gutenberg#85168)
- SelectControl: Fix default options showing the `Select` placeholder (WordPress/gutenberg#85172)
- Actions API: Remove the unsupported `single` action context (WordPress/gutenberg#85186)
- Client-side media: Upgrade wasm-vips to 0.0.19 and raise memory budgets accordingly (WordPress/gutenberg#84980)
- Styles: Fix inconsistent 'Elements' tools panel heading level (WordPress/gutenberg#85247)
- `media-utils`/MediaEdit: use design system focus ring (WordPress/gutenberg#84940)
- Icons: Add new form based icons. (WordPress/gutenberg#84074) (WordPress/gutenberg#85360)
- Navigation: keep custom CSS off inner list containers (WordPress/gutenberg#84881) (WordPress/gutenberg#85367)
- Navigation: keep Global Styles custom CSS off inner list containers (WordPress/gutenberg#85366)
- Edit as HTML: Show design system focus ring on the HTML textarea (WordPress/gutenberg#85266) (WordPress/gutenberg#85359)
- Icons: Restore the missing speech bubble in postComments (WordPress/gutenberg#85275)
- Block Directory: Standardize downloadable block focus indicators (WordPress/gutenberg#85307)
- Global Styles: Add icons and tweak styling for element and block buttons (WordPress/gutenberg#85363) (WordPress/gutenberg#85414)
- Tests: Stop asserting Core lacks the core fields functions (WordPress/gutenberg#85201)
- Meta Boxes: Use the design system focus ring for the panel toggle (WordPress/gutenberg#85355) (WordPress/gutenberg#85410)
- DataViews: Use the design system focus ring for list items. (WordPress/gutenberg#85358) (WordPress/gutenberg#85435)
- Components: Standardize checkbox and radio focus outlines (WordPress/gutenberg#85379) (WordPress/gutenberg#85436)
- UI: Use solid brand highlights for popup items (WordPress/gutenberg#84087)
- Media: Preserve EXIF metadata when converting HEIC to JPEG client-side (WordPress/gutenberg#82040)
- Icons: Add error, info and postComments to the core-admin collection (WordPress/gutenberg#85452)
- UnitControl: Use the design system outline for the unit select focus ring (WordPress/gutenberg#85444)
- Page List: Keep pages visible in the Navigation sidebar in contentOnly (WordPress/gutenberg#85357)
- Icons: Add new asterisk icon (WordPress/gutenberg#85442) (WordPress/gutenberg#85498)
- wp-env: Keep Debian security updates in Bullseye-based images (WordPress/gutenberg#85469)
- Editor: Guard entity preload filters and share entity actions/fields logic (WordPress/gutenberg#85390) (WordPress/gutenberg#85499)
- UI: Scale Spinner stroke width with its size (WordPress/gutenberg#85378)
- [WP 7.2] Fix the block-library TypeScript test project (WordPress/gutenberg#85533)
- Editor: Vertically center the Categories loading spinner (WordPress/gutenberg#85563)
- DataViews: Render table bulk actions outside the table (WordPress/gutenberg#85250) (WordPress/gutenberg#85571)
- Record e2e traces only when a failed test is retried (WordPress/gutenberg#85428)
- Writing flow: fix triple click in a list item selecting the next item (WordPress/gutenberg#85569)
- Build: Limit concurrent wp-build builds (WordPress/gutenberg#79889)
- Icons: Promote Dashicon replacements to `core-admin` and map their Dashicons (WordPress/gutenberg#85541)
  
Props peterwilsoncc, mamaduka.
See #66340

git-svn-id: https://develop.svn.wordpress.org/trunk@64796 602fd350-edb4-49c9-b593-d223f7449a82
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Backported to WP Core Pull request that has been successfully merged into WP Core [Package] wp-build /packages/wp-build [Type] Enhancement A suggestion for improvement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

wp-build: unbounded concurrency causes slowdowns and OOM on projects with many widgets/packages

8 participants