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.
Merge request reports
Activity
added enhancement label
assigned to @jruzicka
added 1 commit
- d120a385 - setup: require jinja<3.1 to prevent breakage
mentioned in merge request knot/knot-resolver!1248 (merged)
mentioned in commit 12e885f5
Please register or sign in to reply