-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packages: Fix published * workspace dependencies #68240
Packages: Fix published * workspace dependencies #68240
Conversation
Flaky tests detected in 748bde8. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/12596055102
|
Size Change: 0 B Total Size: 1.84 MB ℹ️ View Unchanged
|
It looks like I would be happy to cherry-pick it to |
98e7ad7
to
91703f9
Compare
3af7512
to
748bde8
Compare
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 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. |
Thank you for handling it. It was invaluable when debugging npm publishing 🙇🏻 |
What?
Packages are (sometimes) being published with
*
workspace dependencies since #66272. Thenext
anddev
workflows are correctly replacing the*
versions. The cause is currently unclear, but testing indicates that restoringfile:
dependencies may fix the problem.file:
dependencies )*
dependencies)Why?
Workspace dependencies of published packages should depend on a specific version or version range, never
*
. This can cause breakage for consumers as the dependencies may not be correctly updated when updating packages.How?
Try using
file:
dependencies for workspace packages like was used before #66272.Testing Instructions
CI passes.