{"id":2933,"date":"2026-07-13T14:47:27","date_gmt":"2026-07-13T14:47:27","guid":{"rendered":"https:\/\/make.wordpress.org\/systems\/?p=2933"},"modified":"2026-07-15T17:21:24","modified_gmt":"2026-07-15T17:21:24","slug":"build-server-not-removing-files-from-core-svn-wordpress-org-when-it-should","status":"publish","type":"post","link":"https:\/\/make.wordpress.org\/systems\/2026\/07\/13\/build-server-not-removing-files-from-core-svn-wordpress-org-when-it-should\/","title":{"rendered":"Build server not removing files from core.svn.wordpress.org when it should"},"content":{"rendered":"

There have been several recent cases where the build server has not removed files from the core.svn.wordpress.orgWordPress.org<\/span> The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https:\/\/wordpress.org\/<\/a><\/span><\/span><\/span> repository. This is resulting in files persisting and being included in WordPress releases when they should not be.<\/p>\n\n\n\n

For the 7.0 release, three files related to real-time collaboration have been removed in develop.svn.wordpress.org but not core.svn.wordpress.org (see #65325<\/a>).<\/p>\n\n\n\n

During the 7.1 cycle, there are a few more instances of this documented in #65565<\/a>. These files are not yet meant to be included in a final release of WordPress, but were included in the output of the build script until the upstream fix in the Gutenberg repository<\/a> was merged into wordpress-develop<\/code> in [62584]<\/a>. It\u2019s likely the same problem will occur once #65489<\/a> is fixed as well.<\/p>\n\n\n\n

The issue is occurring both for files previously subject to version control that were explicitly deleted in SVNSVN<\/span> Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https:\/\/subversion.apache.org\/.<\/span><\/span><\/span> (the 7.0 files and wp-includes\/blocks\/navigation-link\/shared\/build-css-font-sizes.php<\/code> during the 7.1 cycle), and those that were never versioned and generated as output from the build script (all of the other files listed in #65565<\/a>).<\/p>\n\n\n\n

During 7.0, other files being included unexpectedly were removed by [62069]<\/a> (corresponding core.svn changeset<\/a>). There is still similar logic in place, but it\u2019s not clear why the same is not happening now. When running npm run build<\/code> locally with outdated files in build<\/code>, all files are removed as expected. It seems there may possibly be an issue where files that are \u201cmissing\u201d from an SVN standpoint are not deleted from version control.<\/p>\n\n\n\n

Could someone please look into this so it can be addressed prior to the 7.1 RC1 release scheduled for August 5th?<\/p>\n\n\n#<\/span>prio1<\/a>