chore(deps): tighten peer dependencies for 2.2.0#27
Merged
Conversation
Pin minimum webpack peer versions, mark sass-loader optional, and document required consumer dependencies.
Add publish-npm workflow (based on @wpsyntex/distribute) and expose existing checks as reusable workflows via workflow_call.
Webpack peers are auto-installed from peerDependencies; only @wordpress/scripts is needed for lint and tests.
Add publishConfig and prepublishOnly (lint + test). Simplify publish-npm workflow by relying on prepublishOnly instead of separate CI jobs.
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
1 participant
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?
Release 2.2.0 with explicit minimum webpack peer dependency versions instead of
*, plus an npm publish workflow on GitHub release.Why?
Open peer ranges made consumer installs unpredictable and pulled in vulnerable transitive dependency versions. Explicit minimums align Polylang projects on a safe webpack toolchain. Automated publishing removes manual npm releases.
How?
peerDependencies: "*"with minimum semver ranges (copy-webpack-plugin^14,css-minimizer-webpack-plugin^8,glob^11, etc.).sass-loaderas optional (only needed for SASS ingetReactifiedConfig).@wordpress/scriptsto ^32.6.0 for lint and tests.publishConfigandprepublishOnly(lint+test) before npm publish..github/workflows/publish-npm.yml(based on@wpsyntex/distribute): publishes onrelease: published(stable) orworkflow_dispatch(bleeding edge@next); quality checks run viaprepublishOnly.Test plan
npm installnpm test(44 tests)@wpsyntex/polylang-build-scripts@2.2.0to npm