From 3f492ab9fa574e2937be9c933971573b97b17188 Mon Sep 17 00:00:00 2001 From: Hananel Hazan Date: Tue, 10 Nov 2026 16:31:42 -0500 Subject: [PATCH] ci(dependabot): bump pyproject.toml only when a version leaves its range Routine Dependabot bumps raised the floors in pyproject.toml (pandas>=3.1.1 in #836), which the weakened-tests guard flags as a steering file. With increase-if-necessary, in-range bumps touch poetry.lock only. Co-Authored-By: Claude Opus 5.5 --- .github/dependabot.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index d795bc1a..25f3e41f 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -10,6 +10,11 @@ updates: open-pull-requests-limit: 5 labels: - "dependencies" + # Touch pyproject.toml only when a new version falls outside the allowed + # range (a major bump). Routine bumps then change poetry.lock alone, so the + # test guard, which flags every pyproject.toml change, lets them through + # (#836), and the lowest version BindsNET accepts does not creep up. + versioning-strategy: increase-if-necessary # Minor and patch bumps arrive as a single grouped pull request so routine # maintenance is one review, not twenty. Major bumps stay separate, because # they need to be looked at individually.