Fix doubly-zipped plugin artifacts in GitHub Actions by Copilot · Pull Request #76857 · WordPress/gutenberg

Copilot · 2026-03-27T09:03:28Z

What?

Fixes the double-zipping of the Gutenberg plugin artifact in GitHub Actions. When gutenberg.zip was uploaded, it got re-wrapped in another ZIP by the upload action, requiring users to unzip twice before they could install the plugin.

Why?

GitHub Actions' actions/upload-artifact automatically archives uploaded files into a ZIP, so uploading an existing .zip results in a double-zipped file. Users downloading the artifact from the workflow run page get a ZIP containing a ZIP, and attempting to install it directly in WordPress fails.

actions/upload-artifact@v7.0.0 (already pinned in this repo) introduced archive: false to upload a single file as-is, without re-wrapping it. This PR uses that option for the Gutenberg plugin build only.

The wordpress-develop build artifact (gutenberg-wordpress-develop) is only used internally — consumed by the publish-to-container-registry job in the same workflow, which unzips it and re-compresses to GHCR — so it continues to work with its existing behavior unchanged.

How?

The single shared upload step in build-plugin-zip.yml is split into two conditional steps:

Plugin build (IS_GUTENBERG_PLUGIN: true): Uses archive: false so the artifact is the raw gutenberg.zip, ready to install in WordPress. The artifact name becomes gutenberg.zip (the name input is ignored by the action when archive: false).
WordPress develop build (IS_GUTENBERG_PLUGIN: false): Keeps the original behavior with name: gutenberg-wordpress-develop. No changes to the publish-to-container-registry job.

The create-release job is updated to download the artifact named gutenberg.zip (previously gutenberg-plugin).

Note

The artifact name changes from gutenberg-plugin to gutenberg.zip. This is an unavoidable consequence of using archive: false — the action's documentation explicitly states the name parameter is ignored in that mode and the filename is always used as the artifact name.

Testing Instructions

Trigger the Build Plugin ZIP workflow on this branch (or wait for CI to run on this PR).
Go to the completed workflow run and download the artifact named gutenberg.zip.
Go to WordPress Playground (or any WordPress install).
Navigate to Plugins → Add New → Upload Plugin and upload the downloaded gutenberg.zip.
Verify that the plugin installs successfully — "Plugin installed successfully." — without a "No valid plugins were found" error.

Testing Instructions for Keyboard

N/A — this is a CI/workflow-only change with no UI impact.

Screenshots or screencast

Before	After

Use of AI Tools

This PR was authored with GitHub Copilot (Coding Agent).

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

Agent-Logs-Url: https://github.com/WordPress/gutenberg/sessions/b1b63c54-e526-4184-9511-64598f83e77a Co-authored-by: luisherranz <3305402+luisherranz@users.noreply.github.com>

luisherranz · 2026-03-27T09:38:48Z

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

+            - name: Rename artifact for wordpress-develop build
+              if: ${{ ! matrix.IS_GUTENBERG_PLUGIN }}
+              run: mv gutenberg.zip gutenberg-wordpress-develop.zip
+
            - name: Upload artifact
              uses: actions/upload-artifact@bbbca2ddaa5d8feaa63e36b76fdaad77386f024f # v7.0.0
              with:
-                  name: gutenberg-${{ ! matrix.IS_GUTENBERG_PLUGIN && 'wordpress-develop' || 'plugin' }}
-                  path: ./gutenberg.zip
+                  # When archive is false, the file name is used as the artifact name.
+                  # gutenberg.zip -> artifact "gutenberg.zip" (plugin build)
+                  # gutenberg-wordpress-develop.zip -> artifact "gutenberg-wordpress-develop.zip" (WP develop build)
+                  path: ${{ ! matrix.IS_GUTENBERG_PLUGIN && './gutenberg-wordpress-develop.zip' || './gutenberg.zip' }}
+                  archive: false


@copilot, investigate and report what exactly is the zip for the WordPress develop build used for? Is it used in this repository, or in the wordpress-develop repository?

The gutenberg-wordpress-develop.zip artifact is used only within this repository's workflow, as an internal intermediate step.

Here's the full flow:

The build job (with IS_GUTENBERG_PLUGIN: false) builds a WordPress-core-targeted version of the assets (with wpPlugin.name = "wp" and IS_WORDPRESS_CORE: true) and produces gutenberg.zip.

That ZIP is uploaded as the gutenberg-wordpress-develop.zip artifact.

The publish-to-container-registry job (which also lives in this same workflow file) downloads that artifact, unzips it, re-compresses the files as a .tar.gz, and pushes the result to GitHub Container Registry at ghcr.io/wordpress/gutenberg/gutenberg-wp-develop-build:<sha>.

The wordpress-develop repository doesn't consume the Actions artifact directly — it uses the GHCR tar.gz package produced in step 3. The ZIP artifact itself is never downloaded externally; it's purely an internal hand-off mechanism between the build job and the publish-to-container-registry job within this same workflow run.

@copilot, are the changes in that part of the workflows absolutely necessary if that is internal? Can't this continue to function with a double zip as it has been working until now?

I'm only interested in the final gutenberg.zip.

Good point — the wordpress-develop build side doesn't need the fix. Updated in c6dc156:

The single shared upload step is now split into two conditional steps: the plugin build uses archive: false, and the wordpress-develop build reverts to the original name: gutenberg-wordpress-develop behavior (double-zip intact, publish-to-container-registry fully reverted).

The "Rename artifact" step is removed entirely.

The only remaining change from the original is: plugin build uses archive: false (fixing the double-zip for users) + create-release downloads name: gutenberg.zip (the artifact name set by archive: false).

…nal as-is Agent-Logs-Url: https://github.com/WordPress/gutenberg/sessions/d65f3bcc-6af7-46c5-ab37-83c5ebe9d094 Co-authored-by: luisherranz <3305402+luisherranz@users.noreply.github.com>

github-actions · 2026-03-27T10:24:59Z

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

[Flaky Test] post title and content are editable and blocks can be inserted #76524 in /test/e2e/specs/editor/various/post-content-focus-mode.spec.js

luisherranz · 2026-03-27T11:51:34Z

@copilot, the artifact name has changed from gutenberg-plugin to gutenberg.zip. Is this unavoidable, or can the same artifact name be kept to prevent breaking environments that are integrating this file?

Copilot · 2026-03-27T11:54:08Z

@copilot, the artifact name has changed from gutenberg-plugin to gutenberg.zip. Is this unavoidable, or can the same artifact name be kept to prevent breaking environments that a...

It's unavoidable when using archive: false. The action.yml explicitly documents this behavior:

When archive is false, only a single file can be uploaded. The name of the file will be used as the artifact name (ignoring the name parameter).

The only workaround is renaming the file before uploading — e.g. mv gutenberg.zip gutenberg-plugin.zip — but that gives artifact name gutenberg-plugin.zip, not gutenberg-plugin.

So the choices are:

Keep current approach (archive: false) — fixes double-zip, artifact name becomes gutenberg.zip
Rename file first — fixes double-zip, artifact name becomes gutenberg-plugin.zip (still a change)
Revert to original — keep name: gutenberg-plugin and accept the double-zip

Happy to implement whichever you prefer. If backward compatibility of the gutenberg-plugin artifact name is important, option 3 is the only way to preserve it exactly.

luisherranz · 2026-03-27T11:55:22Z

@copilot, please update the PR description to follow this repository's template, including the What, Why, and How sections. Also, add these two screenshots and testing instructions stating that to test this PR, one must download the artifact and attempt to install it.

Before:

After:

Copilot · 2026-03-27T11:56:34Z

@copilot, please update the PR description to follow this repository's template, including the What, Why, and How sections. Also, add these two screenshots and testing instructions stating that to tes...

Done — the PR description has been updated to follow the repository template with What, Why, How, Testing Instructions, and Screenshots sections, including the before/after screenshots in the standard table format.

luisherranz · 2026-03-27T11:58:45Z

@youknowriad, @adamziel, what do you think? Is this worth it, or could it break unexpected integrations?

Initial plan

92d5245

Copilot AI assigned Copilot and luisherranz Mar 27, 2026

Copilot started work on behalf of luisherranz March 27, 2026 09:03 View session

Fix double-zipping of plugin ZIP artifacts in GitHub Actions

0c06401

Agent-Logs-Url: https://github.com/WordPress/gutenberg/sessions/b1b63c54-e526-4184-9511-64598f83e77a Co-authored-by: luisherranz <3305402+luisherranz@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Fix double zipping of plugin ZIP files in GitHub Actions~~ Fix doubly-zipped plugin artifacts in GitHub Actions Mar 27, 2026

Copilot finished work on behalf of luisherranz March 27, 2026 09:13

Copilot AI requested a review from luisherranz March 27, 2026 09:13

luisherranz reviewed Mar 27, 2026

View reviewed changes

Copilot started work on behalf of luisherranz March 27, 2026 09:39 View session

Copilot finished work on behalf of luisherranz March 27, 2026 09:43

Copilot AI requested a review from luisherranz March 27, 2026 09:43

luisherranz added the [Type] Code Quality Issues or PRs that relate to code quality label Mar 27, 2026

Copilot started work on behalf of luisherranz March 27, 2026 09:46 View session

Simplify: only fix double-zip for plugin build, keep WP develop inter…

c6dc156

…nal as-is Agent-Logs-Url: https://github.com/WordPress/gutenberg/sessions/d65f3bcc-6af7-46c5-ab37-83c5ebe9d094 Co-authored-by: luisherranz <3305402+luisherranz@users.noreply.github.com>

Copilot finished work on behalf of luisherranz March 27, 2026 09:50

Copilot started work on behalf of luisherranz March 27, 2026 11:51 View session

Copilot finished work on behalf of luisherranz March 27, 2026 11:54

Copilot started work on behalf of luisherranz March 27, 2026 11:55 View session

Copilot finished work on behalf of luisherranz March 27, 2026 11:57

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix doubly-zipped plugin artifacts in GitHub Actions#76857

Fix doubly-zipped plugin artifacts in GitHub Actions#76857
Copilot wants to merge 3 commits intotrunkfrom
copilot/remove-double-zipping-artifacts

Copilot AI commented Mar 27, 2026 •

edited

Loading

Uh oh!

luisherranz Mar 27, 2026

Uh oh!

Copilot AI Mar 27, 2026

Uh oh!

luisherranz Mar 27, 2026

Uh oh!

Copilot AI Mar 27, 2026

Uh oh!

github-actions bot commented Mar 27, 2026

Uh oh!

luisherranz commented Mar 27, 2026

Uh oh!

Copilot AI commented Mar 27, 2026

Uh oh!

luisherranz commented Mar 27, 2026

Uh oh!

Copilot AI commented Mar 27, 2026

Uh oh!

luisherranz commented Mar 27, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

Copilot AI commented Mar 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What?

Why?

How?

Testing Instructions

Testing Instructions for Keyboard

Screenshots or screencast

Use of AI Tools

Uh oh!

luisherranz Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

luisherranz Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Mar 27, 2026

Uh oh!

luisherranz commented Mar 27, 2026

Uh oh!

Copilot AI commented Mar 27, 2026

Uh oh!

luisherranz commented Mar 27, 2026

Uh oh!

Copilot AI commented Mar 27, 2026

Uh oh!

luisherranz commented Mar 27, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Copilot AI commented Mar 27, 2026 •

edited

Loading