Skip to content

merge queue: checking #300 on main (fd8289d) - #303

Closed
mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/9a4af3b317
Closed

merge queue: checking #300 on main (fd8289d)#303
mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/9a4af3b317

Conversation

@mergify

@mergify mergify Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged soon. 🎉

#300 is queued for merge on branch main (fd8289d).

This pull request has been created by Mergify to check the mergeability of #300.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: fd8289d544c736e20f0347c68eae580bdba4171d
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 300
    scopes: []
scopes: []
...

sileht and others added 3 commits August 27, 2026 17:17
Mergify reads its configuration from the default branch, so a pull
request that removes 3.9 from the CI matrix would still be gated on a
`Test with Python 3.9` check run that no longer exists, and could never
merge. Drop the requirement first, on its own, exactly like #142 did
before 3.8 was dropped in #140.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XkWQRxh5pfi2Fbuv3Z9wen
Change-Id: I2e80afa6a0e70ac049da3512f43185a57a744e50
Python 3.9 has been end-of-life since October 2025 and no known consumer
of sql-compare is still on it: the monorepo `engine` and `shadow-office`
both declare `requires-python = "~=3.14.0"`. Dropping it unblocks
dependencies that already require 3.10, starting with sqlparse 0.6.0.

This also removes the CI workaround that existed only for 3.9. Poetry
2.4.1 needs Python >=3.10, so the job installed it under a pinned 3.12
and pointed it at the matrix interpreter with `poetry env use`. With a
3.10 floor a single `setup-python` is enough. Without `poetry env use`,
though, poetry picks its interpreter off PATH, and every matrix version
satisfies `python = "^3.10"` - so a wrong pick would test one version
three times and stay green. The added assertion makes that fail loudly
instead.

`[tool.ruff] target-version` is dropped so ruff infers it from
`requires-python`. It said "py312" while the floor was 3.9 and would
have said it while the floor is 3.10; with `preview = true` and `UP`
selected, that makes ruff raise UP040/UP046 with fixes that emit PEP 695
syntax (`type X = int`, `class Box[T]`), which is a SyntaxError on the
3.10 and 3.11 legs. Inferring keeps the two in sync permanently.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XkWQRxh5pfi2Fbuv3Z9wen
Change-Id: I220426d76c471b02a2dc667a816cf2d171da0033
@mergify
mergify Bot deployed to Mergify Merge Protections August 28, 2026 08:34 Active
@mergify mergify Bot mentioned this pull request Aug 28, 2026
@mergify mergify Bot closed this Aug 28, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/9a4af3b317 branch August 28, 2026 08:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant