Skip to content
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

Merged
merged 7 commits into from
Jan 11, 2022

Conversation

zhaoyongjie
Copy link
Member

@zhaoyongjie zhaoyongjie commented Jan 7, 2022

SUMMARY

In order to publish plugins to npm registry, this PR make:

  1. add commit message in lerna.json
  2. update lerna from 3.22.1 to 4.0.0(latest version)
  3. move @superset-ui/plugins from dependencies to peerDependencies in each packages.json of plugins
  4. update version of dependency to "*" (Matches any version)

Why do we use matches any version instead of exact 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

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

"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",
Copy link
Member Author

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
Copy link

codecov bot commented Jan 7, 2022

Codecov Report

Merging #17965 (ddd5a4e) into master (d35da1f) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           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           
Flag Coverage Δ
javascript 53.78% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d35da1f...ddd5a4e. Read the comment docs.

@zhaoyongjie zhaoyongjie force-pushed the fix_release_workflow branch 2 times, most recently from 12ea51f to 6e72879 Compare January 10, 2022 06:34
@zhaoyongjie zhaoyongjie merged commit e91b9a6 into apache:master Jan 11, 2022
shcoderAlex pushed a commit to casual-precision/superset that referenced this pull request Feb 7, 2022
…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
bwang221 pushed a commit to casual-precision/superset that referenced this pull request Feb 10, 2022
…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
@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 1.5.0 labels Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels size/L 🚢 1.5.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants