diff options
| author | Benjamin Bach <benjamin@overtag.dk> | 2022-08-19 23:50:49 +0300 |
|---|---|---|
| committer | Benjamin Bach <benjamin@overtag.dk> | 2022-08-19 23:50:49 +0300 |
| commit | 7c43f45c9bb24611a60747e443985db791d4e85d (patch) | |
| tree | ac6e648cee381c1ec3ab8f5b547a7c90eaf88b5d | |
| parent | 8e737d4c84f43849ae0b9701dc5a8f735ed2f4bd (diff) | |
Do not build the python package in this step
| -rw-r--r-- | docs/contributing.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/contributing.rst b/docs/contributing.rst index f94bc46..e3366bf 100644 --- a/docs/contributing.rst +++ b/docs/contributing.rst @@ -184,8 +184,8 @@ To release a new version of the theme, core team will take the following steps: #. Update the changelog (``docs/changelog.rst``) with the version information. #. Run ``python setup.py update_translations`` to compile new translation files and update Transifex. -#. Run ``npm install && npm run build && python setup.py bdist_wheel sdist`` to rebuild all the theme assets and the Python - package, notice that ``package-lock.json`` will be updated with a new package +#. Run ``npm install && npm run build`` to rebuild all the theme assets, + notice that ``package-lock.json`` will be updated with a new package version. But take care that it isn't also bumping versions of dependencies in ways that are risky to the release. *If* ``package-lock.json`` changes, you need to commit it to git and tag it together with your release. |