From d2a13c55f2ba5083d7b1791573576bcaa6811070 Mon Sep 17 00:00:00 2001 From: Brad Warren Date: Thu, 30 May 2024 11:21:32 -0700 Subject: [PATCH] pin back mypy (#9939) while working on https://github.com/certbot/certbot/issues/9938, i updated our dependencies which updated mypy introducing new errors that mypy wanted me to fix. i think this makes the regularly necessary process of updating our dependencies too tedious and we should instead pin our linters that do this to a specific version and update them manually as desired. we already do this with pylint in the lines above my changes in this PR for the same reason --- tools/pinning/current/pyproject.toml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tools/pinning/current/pyproject.toml b/tools/pinning/current/pyproject.toml index 1034ee8b5..d711e3ffc 100644 --- a/tools/pinning/current/pyproject.toml +++ b/tools/pinning/current/pyproject.toml @@ -62,6 +62,10 @@ setuptools-rust = "*" # If this pinning is removed, we may still need to add a lower bound for the # pylint version. See https://github.com/certbot/certbot/pull/9229. pylint = "3.0.2" +# mypy often adds new checks that we need to conform our code to when updating +# dependencies. To help control when this needs to be done, we pin mypy to a +# compatible version here. +mypy = "1.9.0" # Bug in poetry, where still installes yanked versions from pypi (source: https://github.com/python-poetry/poetry/issues/2453) # this version of cryptography introduced a security vulnrability.