Status : BETA
Release date: 03 December 2025
Pyrefly v0.44.0 bundles 163 commits from 23 contributors.
✨ New & Improved
| Area | What’s new |
|---|---|
| LSP / IDE | - Inlay hints are now clickable, allowing Go-To-Definition for class and type names (e.g., List or T) directly from the hint overlay. - Completions are now disabled inside comments and string literals to reduce noise and improve user experience. |
| Type checking | - Recursive type solving logic was significantly refactored, enabling more reliable type inference and bug fixes around self-referential types. - Bundled typeshed and third-party stubs have been updated, improving compatibility and type checking for more libraries |
| Pydantic/Dataclass | - Added support for Pydantic range constraints (e.g., pydantic.types.PositiveInt). - New infrastructure introduced to better support Pydantic lax mode - Support added for the Decimal type.
|
| Error Handling | Error suppressions are now stricter, only applying when the suppression comment is on the start line, reducing false negatives |
🐛 bug fixes
We closed 11 bug issues this release 👏
- #1692 - fixed an issue where args and kwargs of wrapper functions were wrongly reported as not subscriptable
- #1665 - Prevents unnecessary
Literal[...]tooltips when hovering over docstrings. - #1559 - Updated dependencies to pull in fix for ruff parser that was causing Pyrefly to crash in jupyter notebooks
- #1372 - resolved issue with inherited properties incorrectly being overridden by assignment
- And more: #1371, #1035, #1675, #1701, #1688, #1710, #1719
Thank-you to all our contributors who found these bugs and reported them! Did you know this is one of the most helpful contributions you can make to an open-source project? If you find any bugs in Pyrefly we want to know about them! Please open a bug report issue here
📦 Upgrade
pip install --upgrade pyrefly==v0.44.0
How to safely upgrade your codebase
Upgrading the version of Pyrefly you're using or a third-party library you depend on can reveal new type errors in your code. Fixing them all at once is often unrealistic. We've written scripts to help you temporarily silence them. After upgrading, follow these steps:
pyrefly check --suppress-errors- run your code formatter of choice
pyrefly check --remove-unused-ignores- Repeat until you achieve a clean formatting run and a clean type check.
This will add \# pyrefly: ignore comments to your code, enabling you to silence errors and return to fix them later. This can make the process of upgrading a large codebase much more manageable.
Read more about error suppressions in the [Pyefly documentation](https://pyrefly.org/en/docs/error-suppressions/)
🖊️ Contributors this release
@arthaud, @asukaminato0721 , @connernilsen , @diliop , @fangyi-zhou , @grievejia , @gvozdvmozgu, @Imran-S-heikh, @javabster , @kinto0 , @kshitijgetsac, @migeed-z, @ndmitchell, @ogios, @rchen152, @simonhollis, @stroxler, @yangdanny97, Carlos Fernandez, @dtolnay, @jvansch1, @tianhan0