build_versioned_docs() in build-tools/docs.py calls python setup.py develop against the checked-out source tree:
Howevr, since 1.4.0 dropped setup.py in favor of pyproject.toml. The publish workflow now fails at the docs-publish step on every release going forward.
PR #381 (clams-vocabulary and pyproject.toml migration) updated build_docs_local() to use pip install -e .[docs] but left build_versioned_docs() calling the legacy setup.py develop. The two install paths live in the same file and were updated piecemeal.
Fix
build_versioned_docs()inbuild-tools/docs.pycallspython setup.py developagainst the checked-out source tree:Howevr, since 1.4.0 dropped
setup.pyin favor ofpyproject.toml. The publish workflow now fails at the docs-publish step on every release going forward.PR #381 (
clams-vocabularyandpyproject.tomlmigration) updatedbuild_docs_local()to usepip install -e .[docs]but leftbuild_versioned_docs()calling the legacysetup.py develop. The two install paths live in the same file and were updated piecemeal.Fix
setup.pybefore building a versioned docs. This should keep the legacy path so historical-version docs rebuilds still work