Skip to content

Change the order of the build#10283

Closed
aaronjorbin wants to merge 1 commit into
WordPress:trunkfrom
aaronjorbin:build/change-order
Closed

Change the order of the build#10283
aaronjorbin wants to merge 1 commit into
WordPress:trunkfrom
aaronjorbin:build/change-order

Conversation

@aaronjorbin

@aaronjorbin aaronjorbin commented Oct 15, 2025

Copy link
Copy Markdown
Member

See #10282
See WordPress/gutenberg#72450

Attempt to fix the CI

@github-actions

Copy link
Copy Markdown

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.

Core Committers: Use this line as a base for the props when committing in SVN:

Props jorbin.

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

@github-actions

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@dmsnell dmsnell 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.

For the sake of freeing up merges without CI errors I support this change. We can follow-up with the root issue causing the TypeScript errors.

pento pushed a commit that referenced this pull request Oct 20, 2025
Because of a strange interaction with building Gutenberg from within the plugins directory, TypeScript was appearing to examine code for which it should have no access up the filesystem hierarchy.

This patch changes the order of building Gutenberg so that it occurs before those parent directories contain TypeScript code (by installing the `npm` dependencies) and thus frees up the builds.

This change should not serve as a workaround to avoid fixing the root issue, introduced in WordPress/gutenberg@8401993. Rather, it should be seen as at least a temporary way to remove the trigger of the problem during CI builds.

See also alternative work:

 - To build Gutenberg outside of the plugin directory in https://github.com/WordPress/wordpress-develop/pull/10282/files.
 - To patch the broken `@wordpress/blocks` types inside of `@wordpress/core-data`.

Developed in #10283

Props czarate, desrosj, dmsnell, ellatrix, jorbin, peterwilsoncc, ramonopoly, westonruter, youknowriad.


git-svn-id: https://develop.svn.wordpress.org/trunk@60985 602fd350-edb4-49c9-b593-d223f7449a82
markjaquith pushed a commit to markjaquith/WordPress that referenced this pull request Oct 20, 2025
Because of a strange interaction with building Gutenberg from within the plugins directory, TypeScript was appearing to examine code for which it should have no access up the filesystem hierarchy.

This patch changes the order of building Gutenberg so that it occurs before those parent directories contain TypeScript code (by installing the `npm` dependencies) and thus frees up the builds.

This change should not serve as a workaround to avoid fixing the root issue, introduced in WordPress/gutenberg@8401993. Rather, it should be seen as at least a temporary way to remove the trigger of the problem during CI builds.

See also alternative work:

 - To build Gutenberg outside of the plugin directory in https://github.com/WordPress/wordpress-develop/pull/10282/files.
 - To patch the broken `@wordpress/blocks` types inside of `@wordpress/core-data`.

Developed in WordPress/wordpress-develop#10283

Props czarate, desrosj, dmsnell, ellatrix, jorbin, peterwilsoncc, ramonopoly, westonruter, youknowriad.

Built from https://develop.svn.wordpress.org/trunk@60985


git-svn-id: http://core.svn.wordpress.org/trunk@60321 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actions Bot pushed a commit to platformsh/wordpress-performance that referenced this pull request Oct 20, 2025
Because of a strange interaction with building Gutenberg from within the plugins directory, TypeScript was appearing to examine code for which it should have no access up the filesystem hierarchy.

This patch changes the order of building Gutenberg so that it occurs before those parent directories contain TypeScript code (by installing the `npm` dependencies) and thus frees up the builds.

This change should not serve as a workaround to avoid fixing the root issue, introduced in WordPress/gutenberg@8401993. Rather, it should be seen as at least a temporary way to remove the trigger of the problem during CI builds.

See also alternative work:

 - To build Gutenberg outside of the plugin directory in https://github.com/WordPress/wordpress-develop/pull/10282/files.
 - To patch the broken `@wordpress/blocks` types inside of `@wordpress/core-data`.

Developed in WordPress/wordpress-develop#10283

Props czarate, desrosj, dmsnell, ellatrix, jorbin, peterwilsoncc, ramonopoly, westonruter, youknowriad.

Built from https://develop.svn.wordpress.org/trunk@60985


git-svn-id: https://core.svn.wordpress.org/trunk@60321 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@dmsnell

dmsnell commented Oct 20, 2025

Copy link
Copy Markdown
Member

Merged in 9b9049c
[60985]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants