You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`commands.py` serves as an entry point for utilities to help with plotly.py development.
314
+
315
+
Usage: `python commands.py <subcommand> <args>`
316
+
317
+
| Subcommand | Purpose |
318
+
|------------|---------|
319
+
|`codegen [--noformat]`| Regenerate Python files according to `plot-schema.json`.`--noformat` skips formatter step. |
320
+
|`lint`| Lint all Python code in `plotly/`. |
321
+
|`format`| Format all Python code in `plotly/`. |
322
+
|`updateplotlyjs`| Update `plotly.min.js` and `plot-schema.json` to match the `plotly.js` version specified in `js/package.json`. Then, run codegen to regenerate the Python files. |
323
+
|`updateplotlyjsdev [--devrepo REPONAME --devbranch BRANCHNAME] \| [--local PATH]`| Update `plot-schema.json` and `plotly.min.js` to match the version in the provided plotly.js repo name and branch name, OR local path. Then, run codegen to regenerate the Python files. |
324
+
|`bumpversion X.Y.Z`| Update the plotly.py version number to X.Y.Z across all files where it needs to be updated. |
Copy file name to clipboardExpand all lines: RELEASE.md
+20-11Lines changed: 20 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,10 +7,11 @@ This is the release process for releasing plotly.py version `X.Y.Z`, including c
7
7
8
8
### Finalize changelog
9
9
10
-
Review the contents of `CHANGELOG.md`. We try to follow
10
+
Review the contents of `CHANGELOG.md` under the **Unreleased** header. We try to follow
11
11
the [keepachangelog](https://keepachangelog.com/en/1.0.0/) guidelines.
12
-
Make sure the changelog includes the version being published at the top, along
13
-
with the expected publication date.
12
+
13
+
**Note: You don't need to update the header itself with the new version number,
14
+
as that will be done automatically as part of the next step.**
14
15
15
16
Use the `Added`, `Changed`, `Deprecated`, `Removed`, `Fixed`, and `Security`
16
17
labels for all changes to plotly.py. If the version of plotly.js has
@@ -22,16 +23,24 @@ a link to the plotly.js CHANGELOG.
22
23
23
24
**Create a release branch `git checkout -b release-X.Y.Z`_from the tip of `origin/main`_.**
24
25
25
-
- Manually update the versions to `X.Y.Z` in the files specified below:
26
+
- Ensure that you have `npm` and `uv` installed in your environment
27
+
28
+
- Run the command `python commands.py bumpversion X.Y.Z`, which will update the version to X.Y.Z in the following places
26
29
-`pyproject.toml`
27
-
- update version
28
-
-`CHANGELOG.md`
29
-
- update version and release date
30
-
- finalize changelog entries according to instructions above
30
+
-`uv.lock`
31
+
-`js/package.json`
32
+
-`js/package-lock.json`
33
+
-`CHANGELOG.md` (Adds a new header for X.Y.Z above the unreleased items)
31
34
-`CITATION.cff`
32
-
- update version and release date
33
-
- Run `uv lock` to update the version number in the `uv.lock` file (do not update manually)
34
-
- Commit and push your changes to the release branch:
35
+
36
+
- Run `git diff` and ensure the above files were all updated correctly.
37
+
- Note: The current date is used as the release date in `CHANGELOG.md` and `CITATION.cff`. If you want to use a different date, edit these files manually afterward.
38
+
- If the bumpversion command failed for any reason, you can update the versions yourself by doing the following:
39
+
- Manually update the version number (and release date, as needed) in `pyproject.toml`, `CHANGELOG.md` and `CITATION.cff`
40
+
- Run `npm version X.Y.Z` to update `js/package.json` and `js/package-lock.json`
41
+
- Run `uv lock` to update `uv.lock`
42
+
43
+
- Commit and push the changed files to the release branch:
0 commit comments