From a91fdcd656736e23dcb53342ef1f401a6fe6681a Mon Sep 17 00:00:00 2001 From: Klaas van Schelven Date: Tue, 8 Jul 2025 10:49:33 +0200 Subject: [PATCH] Sentry-SDK requirement, unpin minor version MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit My thinking: * Avoid Dependabot spam for harmless version bumps. (sentry-SDK has the most upgrades by an order of magnitude) * In princple, there should be no breakage, b/c they do semver and "minor version when you add functionality in a backward compatible manner" * This is dev tooling; it shouldn’t be a source of friction. * As it stands: I'm not thoroughly reviewing these anyway (b/c of the spammyness) The alternative would have been to "just freeze" it; if we ever run into problems because of the unpinning I certainly will. --- requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.txt b/requirements.txt index 678a6d9..ad57774 100644 --- a/requirements.txt +++ b/requirements.txt @@ -1,6 +1,6 @@ gunicorn==23.0.* Django==4.2.* -sentry-sdk==2.29.* +sentry-sdk==2.* django-tailwind==3.6.* jsonschema==4.24.* semver==3.0.*