Vips and worker-threads packages: remove private flag so that packages can be published to npm#75752
Merged
andrewserong merged 2 commits intotrunkfrom Feb 20, 2026
Conversation
…s can be published to npm
andrewserong
requested review from
SantosGuillamot and
t-hamano
and removed request for
a team
andrewserong
added
[Type] Bug
|
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 Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @jakebailey. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
6 tasks
|
Size Change: 0 B Total Size: 6.84 MB ℹ️ View Unchanged
|
andrewserong
requested review from
ajitbohra,
fabiankaegy and
juanmaguitar
as code owners
ramonjd
approved these changes
Feb 20, 2026
Member
ramonjd
left a comment
ramonjd
left a comment
There was a problem hiding this comment.
I guess the only way to really test is to merge?
andrewserong
added
the
Backport to Gutenberg RC
Contributor
Author
Thanks for taking a quick look! Yes, I believe that's the case. The e2es failing on this PR are the same that are failing on all PRs right now. Given that this PR is required in order to unblock publishing packages (and the issue flagged in #75718) I'm going to merge without waiting for requirements to be met. |
andrewserong
deleted the
try/allow-vips-and-worker-threads-packages-to-be-published
branch
Member
|
I think we also need to update this line to use a relative path. Line 63 in 5cca19c |
Contributor
Author
Dang, good catch. I'll throw up a quick PR. |
andrewserong
added
the
Backport to WP 7.0 Beta/RC
github-actions
bot
removed
the
Backport to WP 7.0 Beta/RC
gutenbergplugin
pushed a commit
that referenced
this pull request
Feb 20, 2026
…s can be published to npm (#75752) * Vips and worker-threads packages: remove private flag so that packages can be published to npm * Update docs Unlinked contributors: jakebailey. Co-authored-by: andrewserong <andrewserong@git.wordpress.org> Co-authored-by: ramonjd <ramonopoly@git.wordpress.org> Co-authored-by: talldan <talldanwp@git.wordpress.org> Co-authored-by: ockham <bernhard-reiter@git.wordpress.org> Co-authored-by: justlevine <justlevine@git.wordpress.org> Co-authored-by: up1512001 <up1512001@git.wordpress.org> Co-authored-by: joshualip-plaudit <joshualipstone@git.wordpress.org> Co-authored-by: Hug0-Drelon <hugod@git.wordpress.org>
github-actions
bot
added
the
Backported to WP Core
|
I just cherry-picked this PR to the wp/7.0 branch to get it included in the next release: 95a8df1 |
pento
pushed a commit
to WordPress/wordpress-develop
that referenced
this pull request
Feb 20, 2026
CI run: #10988. See #64595. --- I've included a log of the Gutenberg changes with the following command: ``` git log --reverse --format="- %s" b441348bb7e05af351c250b74283f253acaf9138..23b566c72e9c4a36219ef5d6e62890f05551f6cb | sed 's|#\([0-9][0-9]*\)|https://github.com/WordPress/gutenberg/pull/\1|g; /github\.com\/WordPress\/gutenberg\/pull/!d' | pbcopy ``` - Remove experimental property from Icon block (WordPress/gutenberg#75742) - Real-time collab editing: Fix undo E2E test (WordPress/gutenberg#75740) - Snackbar: Fix scaling issue with snackbars that update their content via a common id (WordPress/gutenberg#75709) - Vips and worker-threads packages: remove private flag so that packages can be published to npm (WordPress/gutenberg#75752) - Update wordpress/vips in root package.json to use a relative path (WordPress/gutenberg#75758) - Fix change-detection and new-post E2E tests after RTC enabled by default (WordPress/gutenberg#75751) - Query: Remove content role from block (WordPress/gutenberg#75760) - `ToggleGroupControl`: Make unselected item color consistent across all variants (WordPress/gutenberg#75737) - Icon-block: fix global-styles selectors (WordPress/gutenberg#75724) - RTC: Add cap check for single taxonomy term entities (WordPress/gutenberg#75708) - Core Data: Create icons entity (WordPress/gutenberg#75773) git-svn-id: https://develop.svn.wordpress.org/trunk@61705 602fd350-edb4-49c9-b593-d223f7449a82
markjaquith
pushed a commit
to markjaquith/WordPress
that referenced
this pull request
Feb 20, 2026
CI run: WordPress/wordpress-develop#10988. See #64595. --- I've included a log of the Gutenberg changes with the following command: ``` git log --reverse --format="- %s" b441348bb7e05af351c250b74283f253acaf9138..23b566c72e9c4a36219ef5d6e62890f05551f6cb | sed 's|#\([0-9][0-9]*\)|https://github.com/WordPress/gutenberg/pull/\1|g; /github\.com\/WordPress\/gutenberg\/pull/!d' | pbcopy ``` - Remove experimental property from Icon block (WordPress/gutenberg#75742) - Real-time collab editing: Fix undo E2E test (WordPress/gutenberg#75740) - Snackbar: Fix scaling issue with snackbars that update their content via a common id (WordPress/gutenberg#75709) - Vips and worker-threads packages: remove private flag so that packages can be published to npm (WordPress/gutenberg#75752) - Update wordpress/vips in root package.json to use a relative path (WordPress/gutenberg#75758) - Fix change-detection and new-post E2E tests after RTC enabled by default (WordPress/gutenberg#75751) - Query: Remove content role from block (WordPress/gutenberg#75760) - `ToggleGroupControl`: Make unselected item color consistent across all variants (WordPress/gutenberg#75737) - Icon-block: fix global-styles selectors (WordPress/gutenberg#75724) - RTC: Add cap check for single taxonomy term entities (WordPress/gutenberg#75708) - Core Data: Create icons entity (WordPress/gutenberg#75773) Built from https://develop.svn.wordpress.org/trunk@61705 git-svn-id: http://core.svn.wordpress.org/trunk@61013 1a063a9b-81f0-0310-95a4-ce76da25c4cd
|
Guys, how long would it take to publish hotfix or new version to NPM? Our production sites with |
ockham
added a commit
that referenced
this pull request
Feb 23, 2026
…s can be published to npm (#75752) * Vips and worker-threads packages: remove private flag so that packages can be published to npm * Update docs Unlinked contributors: jakebailey. Co-authored-by: andrewserong <andrewserong@git.wordpress.org> Co-authored-by: ramonjd <ramonopoly@git.wordpress.org> Co-authored-by: talldan <talldanwp@git.wordpress.org> Co-authored-by: ockham <bernhard-reiter@git.wordpress.org> Co-authored-by: justlevine <justlevine@git.wordpress.org> Co-authored-by: up1512001 <up1512001@git.wordpress.org> Co-authored-by: joshualip-plaudit <joshualipstone@git.wordpress.org> Co-authored-by: Hug0-Drelon <hugod@git.wordpress.org>
Contributor
|
I just cherry-picked this PR to the release/22.6 branch to get it included in the next release: d17a37e |
ockham
removed
the
Backport to Gutenberg RC
ockham
added a commit
that referenced
this pull request
Feb 23, 2026
…s can be published to npm (#75752) * Vips and worker-threads packages: remove private flag so that packages can be published to npm * Update docs Unlinked contributors: jakebailey. Co-authored-by: andrewserong <andrewserong@git.wordpress.org> Co-authored-by: ramonjd <ramonopoly@git.wordpress.org> Co-authored-by: talldan <talldanwp@git.wordpress.org> Co-authored-by: ockham <bernhard-reiter@git.wordpress.org> Co-authored-by: justlevine <justlevine@git.wordpress.org> Co-authored-by: up1512001 <up1512001@git.wordpress.org> Co-authored-by: joshualip-plaudit <joshualipstone@git.wordpress.org> Co-authored-by: Hug0-Drelon <hugod@git.wordpress.org>
Contributor
|
I just cherry-picked this PR to the wp/latest branch to get it included in the next release of npm packages: 8420cc9 |
24 tasks
Contributor
|
@NumberOneBot This should be fixed now, per #75718 (comment). Can you try and see if it works for you? |
|
@ockham Yes, it works now, thanks. |
|
Thank you so much, it works! |
scruffian
pushed a commit
that referenced
this pull request
Feb 23, 2026
…s can be published to npm (#75752) * Vips and worker-threads packages: remove private flag so that packages can be published to npm * Update docs Unlinked contributors: jakebailey. Co-authored-by: andrewserong <andrewserong@git.wordpress.org> Co-authored-by: ramonjd <ramonopoly@git.wordpress.org> Co-authored-by: talldan <talldanwp@git.wordpress.org> Co-authored-by: ockham <bernhard-reiter@git.wordpress.org> Co-authored-by: justlevine <justlevine@git.wordpress.org> Co-authored-by: up1512001 <up1512001@git.wordpress.org> Co-authored-by: joshualip-plaudit <joshualipstone@git.wordpress.org> Co-authored-by: Hug0-Drelon <hugod@git.wordpress.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What? Why? How?
Hopefully fixes #75718
The
@wordpress/vipsand@wordpress/worker-threadspackages aren't available on npm, which appears to be the cause of failures reported in #75718.In order to allow these packages to be installed, remove the
privateflag for these packages. This should hopefully unblock publishing to npm, and then once published, 🤞 #75718 should be resolved.Testing Instructions
Shouldn't change anything in Gutenberg, but if you'd like, smoke test that uploading media in Gutenberg works as expected.