-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected mkdocs
build failure: not using project's installed mkdocs
extensions.
#11167
Comments
Also facing this issue, our builds using poetry are suddenly failing. Have also made no changes to RTD or Poetry configuration. In our case the error is:
Edit: Appears to be related to #11150 and #11152. Updating |
mkdocs
build failure: not using project's installed mkdocs
extensions.
Thanks for that edit @collindutter, I hadn't seen #11152 and can confirm that using |
Details
Expected Result
I'm making sure a release branch builds MkDocs pages correctly on RTD. Recent releases on the same project built without problem. See for example, this build from last week, which succeeded:
https://readthedocs.org/projects/safedata-validator/builds/23516950/
Actual Result
The new code doesn't have any changes to the RTD configuration or build process, but it fails. The package is installed using
poetry
and thepyproject.toml
file includes all of the packages required to build the documentation in thedocs
group. I usepoetry install --with docs
to install the package requirements.Looking at the logs, both builds successfully install via
poetry
. The earlier successful build then gets to the build step:python -m pip install --upgrade --no-cache-dir mkdocs
and immediately finds all the required packages that have been installed bypoetry
. The failing build gets to the same step and does not find those installs, so installs the RTD standardmkdocs
suite of packages and not the extra requirements included inpoetry
. So it fails whenmkdocs
tries to use those extensions.I can't see what is causing this - I don't think I've changed anything that impacts this!
The text was updated successfully, but these errors were encountered: