-
Notifications
You must be signed in to change notification settings - Fork 56
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
Build failed, probable dependency version conflict #821
Comments
Yes, this repeated for handbook build on github actions after a recent PR. Read the docs builds seems unaffected. The corresponding RTD build succeeded and the handbook has recent changes. Could be because on RTD we use python 3.7 (specified in |
adswa
added a commit
that referenced
this issue
Apr 13, 2022
adswa
added a commit
that referenced
this issue
Jan 30, 2024
It was introduced in response to #821, but the underlying issue seems resolved (no import error during linkcheck). An upgrade is necessary because of a vulnerability report in Jinja2, which was patched in version 3.1.3. Vulnerability report: https://github.com/datalad-handbook/book/security/dependabot/1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The latest monthly link check failed with:
Google leads to this issue in Sphinx which says that deprecations in Jinja2 are the cause. Suggested workaround is to pin
jinja2 < 3.1
(consistent with the fact that the failed build used 3.1.1, while the last successful used 3.0.3). A proper fix would be to unpin Sphinx itself (currently we havesphinx==2.1.2
) and use the latest version, currently 4.5 (which is a big leap).If readthedocs build fail too, we will need to pin Jinja2, and maybe consider updating Sphinx later on.
The text was updated successfully, but these errors were encountered: