-
Notifications
You must be signed in to change notification settings - Fork 794
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
build: Strip workspace refs from mirrors #23654
Conversation
It's annoying to have to update all the dependencies of monorepo JS packages for every patch-level version bump. Let's make it work like the PHP dependencies, where the dependencies are only updated on minor and major bumps. The new scheme looks like `workspace:* || ^1.2`. Within the monorepo the `workspace:*` part is operative and the `^1.2` is ignored by pnpm but will still be checked by CI. When we publish we can strip the `workspace:* || ` bit leaving only the `^1.2` for external users. But I'll save that change for a followup PR.
They aren't going to be valid in the mirrors anyway, and when it comes to JS packages they might confuse things. Best to strip them out, leaving just the "public" version number.
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available. Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped. Jetpack plugin:
Backup plugin:
Social plugin:
Starter Plugin plugin:
Protect plugin:
|
…rip-js-workspace-refs
Changes proposed in this Pull Request:
They aren't going to be valid in the mirrors anyway, and when it comes
to JS packages they might confuse things. Best to strip them out,
leaving just the "public" version number.
Jetpack product discussion
none
Does this pull request change what data or activity we track or use?
no
Testing instructions: