-
Notifications
You must be signed in to change notification settings - Fork 13.9k
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
refactor: move superset-ui dependencies to peerDependencies #17965
Conversation
bb93b00
to
72a985a
Compare
"plugins:create-conventional-version": "npm run prune && lerna version --conventional-commits --create-release github --yes", | ||
"plugins:create-minor-version": "npm run prune && lerna version minor --yes", | ||
"plugins:create-patch-version": "npm run prune && lerna version patch --yes", | ||
"plugins:create-conventional-version": "npm run prune && lerna version --conventional-commits --create-release github --no-private --yes", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do not change version of private package: superset-ui-demo
Codecov Report
@@ Coverage Diff @@
## master #17965 +/- ##
=======================================
Coverage 67.10% 67.10%
=======================================
Files 1612 1612
Lines 64992 64992
Branches 6871 6871
=======================================
Hits 43615 43615
Misses 19510 19510
Partials 1867 1867
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
12ea51f
to
6e72879
Compare
6e72879
to
ddd5a4e
Compare
…7965) * chore: add commit message * update learn * update superset-ui-demo * move superset-ui into peerDeps * add --no-private argument in lerna version * fix conflicts * refresh lock file
…7965) * chore: add commit message * update learn * update superset-ui-demo * move superset-ui into peerDeps * add --no-private argument in lerna version * fix conflicts * refresh lock file
SUMMARY
In order to publish plugins to
npm
registry, this PR make:lerna.json
lerna
from3.22.1
to4.0.0
(latest version)@superset-ui/plugins
fromdependencies
topeerDependencies
in eachpackages.json
of pluginsWhy do we use
matches any version
instead ofexact version
?If we use
exact version
,lerna version
command will update dependency to a new version that doesn't exist in the npm registry. CI will fail.BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
N/A
TESTING INSTRUCTIONS
CI
ADDITIONAL INFORMATION