@@ -32,6 +32,8 @@ a link to the plotly.js CHANGELOG.
32
32
Manually update the versions to ` X.Y.Z ` in the files
33
33
specified below.
34
34
35
+ - ` packages/python/plotly/README.md `
36
+ + this must be done at this point because the README gets baked into PyPI
35
37
- ` plotly/_widget_version.py ` :
36
38
+ Update ` __frontend_version__ ` to ` ^X.Y.Z ` (Note the ` ^ ` prefix)
37
39
- ` packages/javascript/plotlywidget/package.json `
@@ -59,6 +61,18 @@ Make sure tests pass CI checks, then tag this commit as `vX.Y.Z` (e.g. `v3.1.1`)
59
61
(plotly_dev) $ git push origin vX.Y.Z
60
62
```
61
63
64
+ ### Publish JS Extensions to NPM
65
+
66
+ Build and publish the final version of the extensions to NPM. We do this first because
67
+ once we push to PyPI the README will refer to these versions.
68
+
69
+ ``` bash
70
+ cd packages/javascript/jupyterlab-plotly
71
+ npm run build && npm publish --access public
72
+ cd packages/javascript/plotlywidget
73
+ npm run build && npm publish --access public
74
+ ```
75
+
62
76
### Publishing to PyPI
63
77
64
78
Build and publish the final version to PyPI
@@ -81,17 +95,6 @@ $ pip install plotly --upgrade
81
95
82
96
And ask one of your friends to do it too. Our tests should catch any issues, but you never know.
83
97
84
- ### Publish JS Extensions to NPM
85
-
86
- Finally, publish the final version of the extensions to NPM with:
87
-
88
- ``` bash
89
- cd packages/javascript/jupyterlab-plotly
90
- npm run build && npm publish --access public
91
- cd packages/javascript/plotlywidget
92
- npm run build && npm publish --access public
93
- ```
94
-
95
98
### Publishing to the plotly conda channel
96
99
97
100
To publish package to the plotly anaconda channel you'll need to have the
0 commit comments