Docs: Fix build by pinning sphinx-autoapi~=3.0.0
#1038
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The more recent release v3.1.0 of `sphinx-autoapi` causes the build to fail because there are warnings about the generated API files not being found. The exact cause of the bug is unknown as of yet and therefore, as a workaround we are pinning the dependency for now.
mikibonacci
pushed a commit
to mikibonacci/aiida-quantumespresso
that referenced
this pull request
Aug 22, 2024
The more recent release v3.1.0 of `sphinx-autoapi` causes the build to fail because there are warnings about the generated API files not being found. The exact cause of the bug is unknown as of yet and therefore, as a workaround we are pinning the dependency for now.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The more recent release v3.1.0 of
sphinx-autoapicauses the build to fail because there are warnings about the generated API files not being found. The exact cause of the bug is unknown as of yet and therefore, as a workaround we are pinning the dependency for now.