Do not bump the version in auto-maintained file package-lock.json

2 files changed, 4 insertions, 6 deletions

diff --git a/docs/contributing.rst b/docs/contributing.rst
index 9eedb03..f4ed282 100644
--- a/docs/contributing.rst
+++ b/docs/contributing.rst
@@ -184,8 +184,10 @@ 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 run build`` to rebuild all the theme assets and the Python
+   package, 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.
 #. Commit these changes.
 #. Tag the release in git: ``git tag $NEW_VERSION``.
 #. Push the tag to GitHub: ``git push --tags origin``.
diff --git a/setup.cfg b/setup.cfg
index d105f7c..cd69fbe 100644
--- a/setup.cfg
+++ b/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}