From a1855206f7e80db464305b5f85aaad81d1c0a5ca Mon Sep 17 00:00:00 2001 From: Artur Shiriev Date: Tue, 22 Sep 2026 19:03:52 +0300 Subject: [PATCH] docs(ci): correct what the lowest leg is said to guard The comment credited the 0.13.2 -> 0.7.6 breakage to the declared floor. `git show 0.13.2:pyproject.toml` says `faststream>=0.7.1,<0.8`, and 0.7.6 is inside that range: the break came from resolving newest, which `pytest` already covers, and a leg resolving `lowest-direct` would have installed 0.7.1 and passed. The floor was raised to 0.7.6 in #182 because adapting to the new API dropped support for 0.7.1-0.7.5, not because the floor was untested. Replaced with this repo's own floor failure, the one #186 fixed: `sqlalchemy[asyncio]>=2.0` installs on 3.13 and then fails at import, because SQLAlchemy's TypingOnly check rejects the `__firstlineno__` and `__static_attributes__` attributes 3.13 added. Nothing but this leg installs that version. Comment only; no job behaviour changes. --- .github/workflows/_checks.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/_checks.yml b/.github/workflows/_checks.yml index 0f7b3c1..baa580e 100644 --- a/.github/workflows/_checks.yml +++ b/.github/workflows/_checks.yml @@ -87,7 +87,7 @@ jobs: lowest: # The declared floors are part of what we ship, and nothing else in CI installs # them: `pytest` and `scheduled-dep-check` both resolve highest. That is how - # 0.13.2 shipped `faststream>=0.7.1` and stayed green until 0.7.6 broke a user. + # `sqlalchemy[asyncio]>=2.0` stayed declared after 3.13 made it fail at import. # This leg resolves the lower bound instead, on every supported interpreter: # a floor's wheel coverage is per-interpreter, so two interpreters resolving # the same versions can still disagree on whether those versions install.