setup: require jinja<3.1 to prevent breakage (!115) · Merge requests · packaging / apkg · GitLab

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.

Jakub Ružička requested to merge jinja31-counter into master Jun 30, 2022

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.