setup: require jinja<3.1 to prevent breakage
Jinja 3.1 breaks many things due to removal of obsolete features and sometimes it's pulled in by apkg during pip install apkg Stay on <3.1 for now until this mess is fixed across the ecosystem.
parent
4773ae35
No related branches found
No related tags found
Pipeline #101342 failed
Stage: test
Stage: apkg
Stage: bird
Stage: libyang
Stage: knot-dns
Stage: knot-resolver
... | ... | @@ -4,7 +4,7 @@ build # apkg distribution |
cached_property # @cached_property for python <= 3.7 | ||
click # nice CLI framework | ||
distro # current distro detection | ||
jinja2 # templating | ||
jinja2<3.1 # templating (COMPAT: <3.1 in order not to break systems, apkg works fine) | ||
packaging # version parsing | ||
requests # HTTP for humans™ | ||
toml # config files |
-
mentioned in commit 9281f520
-
mentioned in merge request !123 (merged)
Please register or sign in to comment