Tentative fix of the build #8025
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
|
it seems this is working @offtherailz |
offtherailz
approved these changes
Mar 25, 2022
|
Approved. It needs to be backported |
MV88
added
the
BackportNeeded
MV88
added a commit
to MV88/MapStore2
that referenced
this pull request
Mar 25, 2022
tdipisa
removed
the
BackportNeeded
MV88
added a commit
that referenced
this pull request
Mar 25, 2022
12 tasks
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.
Description
here they say to fix jinja version to avoid build to fail
mkdocs/mkdocs#2794 (comment)
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
build of mkdocs fails
for example
https://readthedocs.org/projects/mapstore/builds/16464935/
What is the new behavior?
to not have them failing
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information