Release tools: Move the plugin ZIP build out of bin/

.github/CODEOWNERS

@@ -25,6 +25,7 @@
 /packages/interactivity                         @luisherranz @darerodz
 
 # Tooling
+# Emptied out by #83033; the entry stays so anything reappearing there gets reviewed.
 /bin                                            @manzoorwanijk
 /tools                                          @manzoorwanijk
 /test/php/gutenberg-coding-standards            @anton-vlasenko

.github/workflows/build-plugin-zip.yml

@@ -260,7 +260,7 @@ jobs:
               run: jq --tab '.wpPlugin.name = "wp"' package.json > package.json.tmp && mv package.json.tmp package.json
 
             - name: Build Gutenberg plugin ZIP file
-              run: ./bin/build-plugin-zip.sh
+              run: npm run build:plugin-zip
               env:
                   NO_CHECKS: 'true'
                   IS_GUTENBERG_PLUGIN: ${{ matrix.IS_GUTENBERG_PLUGIN }}

.github/workflows/performance.yml

@@ -201,7 +201,7 @@ jobs:
               if: steps.reused.outputs.ok != 'true'
               run: npm run build -- --skip-types || npm run build
 
-            # The list comes from bin/plugin-files.txt on the tested commit, so older refs
+            # The list comes from tools/release/plugin-files.mts on the tested commit, so older refs
             # are packaged the same way. They may lack some of the files.
             - name: Package plugin
               if: steps.reused.outputs.ok != 'true'

docs/contributors/code/getting-started-with-code-contribution.md

@@ -198,7 +198,7 @@ To build: open a terminal (or if on Windows, a command prompt) and navigate to t
 
 After building the cloned gutenberg directory contains the complete plugin, you can upload the entire repository to your `wp-content/plugins` directory and activate the plugin from the WordPress admin.
 
-Another way to upload after building is to run `npm run build:plugin-zip` to create a plugin zip file — this requires `bash` and `php` to run. The script creates `gutenberg.zip` that you can use to install Gutenberg through the WordPress admin.
+Another way to upload after building is to run `npm run build:plugin-zip`, which creates a `gutenberg.zip` that you can use to install Gutenberg through the WordPress admin.
 
 ## Storybook
 

package.json

@@ -114,7 +114,7 @@
 	"scripts": {
 		"agents:setup": "npm run --workspace @wordpress/agent-tools setup --",
 		"build": "npm run --workspace @wordpress/build-scripts build:all --",
-		"build:plugin-zip": "bash ./bin/build-plugin-zip.sh",
+		"build:plugin-zip": "npm run --workspace @wordpress/release-tools build-plugin-zip --",
 		"check:type-declarations": "npm run --workspace @wordpress/build-scripts check-type-declarations --",
 		"clean:package-types": "npm run --workspace @wordpress/build-scripts clean:package-types --",
 		"clean:packages": "npm run --workspace @wordpress/build-scripts clean:packages --",

phpcs.xml.dist

@@ -45,7 +45,6 @@
 	<!-- Check up to 20 files simultaneously. -->
 	<arg name="parallel" value="20"/>
 
-	<file>./bin</file>
 	<file>./gutenberg.php</file>
 	<file>./lib</file>
 	<file>./packages</file>

tools/monorepo/package.json

@@ -21,6 +21,7 @@
 	"bugs": {
 		"url": "https://github.com/WordPress/gutenberg/issues"
 	},
+	"type": "module",
 	"exports": {
 		"./tsconfig/*": "./tsconfig/tsconfig.*"
 	},