Don't run bumpversion on package-lock.json

docs/contributing.rst

@@ -184,8 +184,11 @@ 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 ``python setup.py build_assets`` to rebuild all the theme assets and the Python
-   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.
 #. Commit these changes.
 #. Tag the release in git: ``git tag $NEW_VERSION``.
 #. Push the tag to GitHub: ``git push --tags origin``.

setup.cfg

@@ -49,10 +49,6 @@ first_value = 1
 search = "version": "{current_version}",
 replace = "version": "{new_version}",
 
-[bumpversion:file:package-lock.json]
-search = "version": "{current_version}",
-replace = "version": "{new_version}",
-
 [bumpversion:file:docs/changelog.rst]
 search = .. |development_version| replace:: {current_version}
 replace = .. |development_version| replace:: {new_version}

setup.py

@@ -130,6 +130,7 @@ def run(self):
             'transifex-client',
             'sphinxcontrib-httpdomain',
             'bump2version',
+            'wheel',
         ],
     },
     classifiers=[