Version 0.0.26 introduced a type-checking error for sqlmodel.Field

[jakekasan]

First Check

• I added a very descriptive title here.
• I used the GitHub search to find a similar question and didn't find it.
• I searched the SQLModel documentation, with the integrated search.
• I already searched in Google "How to X in SQLModel" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answer.
• I already checked if it is not related to SQLModel but to Pydantic.
• I already checked if it is not related to SQLModel but to SQLAlchemy.

Commit to Help

• I commit to help with one of those options 👆

Example Code

from sqlmodel import Field

Description

From 0.0.26 onwards, importing/using sqlmodel.Field and having pyright/basedpyright in "strict" mode causes the type checker to report an error. This means that I either have to set a type: ignore or dial back the overall type "strict-ness" in a project to stop the LSP from complaining.

Full example:

(the code above saved as "main.py")

pyproject.toml - minimal just to set "strict" mode for type-checking

[project]
name = "foo"
version = "0.1.0"
requires-python = ">=3.13"

[tool.pyright]
typeCheckingMode = "strict"

run with version 0.0.25 - no errors or warnings reported (as expected)

pip install --quiet sqlmodel==0.0.25 && pyright

version 0.0.26 fails with reportUnknownVariableType

pip install --quiet sqlmodel==0.0.26 && pyright

Operating System

macOS

Operating System Details

No response

SQLModel Version

0.0.26

Python Version

3.13.7

Additional Context

No response

[YuriiMotov]

This is caused by from __future__ import annotations in main.py added by #1560

[markacianfrani]

I think this might also be related and/or to pyright 1.1.407 specifically