Skip to content

Releases

Pyrefly v1.1.1

Choose a tag to compare

@github-actions github-actions released this 18 Jun 23:46

Release date: June 18, 2026

Pyrefly v1.1.1 is a patch release with a single bug fix.


🐛 Bug fixes

  • #3867: Fixed a regression introduced in 1.1.0 where isinstance() narrowing of a union variable silently stopped working when an earlier sibling branch in the same if/elif/else chain narrowed a different variable with isinstance() and returned. The later narrowing left the union untouched, producing false missing-attribute errors on code that checked correctly in 1.0.0.

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==1.1.1

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:

  1. pyrefly check --suppress-errors
  2. Run your code formatter of choice
  3. pyrefly check --remove-unused-ignores
  4. 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 Pyrefly documentation.

Pyrefly v1.1.0

Choose a tag to compare

@github-actions github-actions released this 17 Jun 16:05

Release date: June 17, 2026

Pyrefly v1.1.0 bundles 788 commits from 72 contributors.


✨ New & Improved

Type Checking

  • Pyrefly now correctly narrows TypedDict types after isinstance(x, dict) checks, treating them as runtime dict instances while preserving field information in the positive branch.
  • Type narrowing for bounded and constrained TypeVars has been significantly improved. isinstance checks now correctly narrow Self and bounded type variables via their disjoint-base representatives, and negative narrowing on bounded TypeVars no longer produces false positives.
  • Constrained TypeVars are now preserved through method calls and binary operations, so T & int where T: (int, str) correctly returns T & int instead of losing the TypeVar.
  • Classes decorated with @dataclass(slots=True) are now recognized as PEP 800 disjoint bases when they synthesize non-empty __slots__, enabling proper multiple-inheritance conflict detection and type narrowing.
  • Pyrefly now detects when methods override parent class methods without using the @override decorator, and a new quick fix can automatically add the decorator for you.
  • Variance inference now correctly skips receiver parameters (like self and cls) when determining class variance, fixing false invariance reports for container-like classes.

Performance

  • File discovery now uses the ignore crate with parallel traversal, making initial indexing 2-3x faster and dramatically reducing wall-clock time for large projects.
  • Completed calculation results are now stored outside the mutex, reducing lock contention and improving performance on large codebases like homeassistant-core and transformers.
  • Implicit builtins are now lazily materialized on first use instead of eagerly adding hundreds of import bindings to every module, reducing memory usage by 5-13% and CPU time by 10-28%.
  • Literal unions are now capped at 256 non-enum literals or 4096 enum members per kind to prevent exponential type growth, and overall union size is capped at 4096 members.
  • Bytes literals larger than 1024 bytes are now widened to bytes to keep type representations bounded.
  • Wide tuple unions (more than 8 variants) are now collapsed into unbounded tuple types to prevent performance hangs and out-of-memory errors during type checking.

Language Server

  • Hover tooltips now work correctly on subscript expressions without spaces (e.g., c[0]), showing the __getitem__ signature instead of garbled output.
  • Literal completions are now offered in expected-type contexts like annotated assignments, return statements, and attribute targets, not just call arguments.
  • Dictionary key completions now work in empty subscripts (d[) and half-typed subscripts (d["), suggesting known keys from TypedDicts and narrowed facets.
  • Go-to-definition on from X import Y statements now falls back to the module file when the imported name can't be resolved (e.g., for non-Python modules like .thrift files).
  • Quick fixes now use the file's actual line ending (CRLF or LF) instead of hardcoded \n, preventing mixed line endings.
  • Added support for legacy pkgutil-style namespace packages

Type Server Protocol (TSP)

  • The TSP backend now emits resolvable typing classes and TypeVars instead of opaque builtins, so hovering over special forms like Literal, Final, and ParamSpec now shows the correct name instead of Unknown.
  • Function types in TSP responses now carry specialized parameter and return types, enabling Pylance to display real types instead of Unknown.
  • Pyrefly now emits the protocol-conformant lowercase unknown sentinel in TSP responses instead of uppercase Unknown.
  • Expected-type queries now return the contextually expected type (e.g., the parameter type for a call argument) instead of the computed type, making the typeServer/getExpectedType request actually useful.

Error Reporting

  • No-matching-overload errors now show only the parameters relevant to the arguments you passed, hiding irrelevant optional parameters to make signatures easier to read.
  • Arity mismatch details and call errors are now included in no-matching-overload error messages, making it clearer why an overload didn't match.
  • The None hint in error messages now only suggests narrowing when it makes sense (e.g., in conditionals) and only suggests adding | None when you control the type.
  • Variance errors on overloaded methods now point to the offending overload instead of always pointing to the first one.

Configuration

  • The tensor-shapes config option has been removed. Tensor shape support is now automatically derived from whether shape_extensions is resolvable for the module being checked.
  • Pyrefly now understands $MYPY_CONFIG_FILE_DIR when migrating mypy configs, stripping it to produce portable relative paths.
  • Glob patterns in config files now require / separators (not OS-specific separators) for cross-platform consistency.

🐛 Bug fixes

We closed 89 bug issues this release 👏

  • #3671: Fixed a stack overflow crash when a descriptor's __get__ method is itself a descriptor. Pyrefly now detects this self-referential case and terminates instead of recursing indefinitely.
  • #3712: Fixed a crash when instantiating a nested functional NamedTuple in constructor defaults. Pyrefly now calls ensure_expr on the default value to avoid panicking during binding.
  • #3789: Fixed a panic ("a variable has leaked from one module to another") when opening sympy/core/expr.py in the LSP. The lambda parameter cache is now keyed by (ModuleName, ModulePath, LambdaParamId) to distinguish in-memory and on-disk module versions.
  • #3749: Fixed a false positive incompatible-overload-residual error on functools.reduce(operator.*, ...). The overload resolves correctly; the spurious diagnostic has been removed.
  • #3819: Fixed unsupported-operation errors when matching on overloads. Protocol conformance now filters overloads by self: type, so a timedelta receiver correctly selects the matching overload instead of erroneously picking the first one.
  • #3751: Pyrefly now rejects @dataclass decorators on NamedTuple classes, matching CPython's runtime behavior which raises a TypeError.
  • #3773: Optional imports like try: import a except ImportError: a = None are no longer reported as untyped by pyrefly coverage.
  • #357: Runtime-evaluated annotations now report uninitialized forward names for Python < 3.14 unless from __future__ import annotations is active, matching CPython's behavior.
  • #3624: pyrefly coverage report no longer includes definitions from if __name__ == "__main__" guards, as those aren't importable at runtime.
  • #3387: Foo[Bar] under from __future__ import annotations now binds Bar as static type information when Foo is a known class, avoiding false "uninitialized" diagnostics.
  • And more! #2798, #3188, #3385, #3208, #3237, #3378, #3413, #3455, #3392, #3299, #3446, #3448, #3396, #1492, #2451, #3431, #3210, #3381, #2547, #3147, #3524, #3506, #3519, #3343, #3505, #3369, #3344, #3400, #3394, #3221, #3514, #3520, #3544, #3458, #3593, #3548, #3576, #3292, #3526, #2869, #3228, #3578, #3568, #3410, #3602, #3300, #3356, #3607, #3612, #1496, #3623, #3059, #3598, #3536, #3066, #3418, #3235, #3673, #3541, #3169, #3075, #1838, #3550, #955, #2711, #498, #3113, #3197, #3215, #1592, #2002, #2082, #2199, #2553, #2693, #3220, #2751, #3743, #3790, #3708, #3703

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==1.1.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:

  1. pyrefly check --suppress-errors
  2. Run your code formatter of choice
  3. pyrefly check --remove-unused-ignores
  4. 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 Pyrefly documentation.


🖊️ Contributors this release

@rchen152, @grievejia, @kinto0, @yangdanny97, @jorenham, @samwgoldman, @connernilsen, @stroxler, @shobhitmehro, @asukaminato0721, @javabster, @NathanTempest, David Tolnay, @mikeleppane, @maggiemoss, @arthaud, Eric Hou, Gregory Carlin, @thatfunkymunki, @hrolfurgylfa, @nitishagar, @tobyh-canva, @vivekjm, @QEDady, @rchiodo, @mdbernard


Please note: These release notes summarize major updates and features. For brevity, not all individual commits are listed.

Pyrefly v1.1.0-dev.2

Pyrefly v1.1.0-dev.2 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 10 Jun 21:31

Release date: June 10, 2026

About dev releases
Dev releases (versions like X.Y.Z-dev.N) are non-stable snapshots cut periodically from trunk. They give early adopters a chance to try in-progress features and surface issues before the next stable release, but they don't carry the same stability or compatibility guarantees as a stable release — don't pin production projects to a dev version.

Pyrefly v1.1.0-dev.2 bundles 250 commits from 37 contributors.


✨ New & Improved

Type Checking

  • Improved handling of defaults for function parameters annotated with type variables. Parameters like x: T = 0 now correctly validate their defaults against the type variable's constraints or bounds, and the default value is properly used when solving type variables in function calls.
  • Enhanced type narrowing for constrained type variables. Operations like isinstance checks and binary operations now preserve the type variable while correctly narrowing to specific constraints, fixing several false positives and negatives.
  • Improved handling of methods on type variables. When calling methods on a type variable (e.g., x.lower() where x: T with T constrained to bytes | str), the return type now correctly preserves the type variable when the method returns self's type.
  • Better support for shaped arrays across libraries. The tensor shape machinery now works with any array class that opts in via shape_extensions.shaped_array, including numpy.ndarray and jax.Array, not just PyTorch tensors.
  • Improved literal promotion and handling in function parameter defaults, making type inference more predictable when defaults include literal values.
  • Fixed handling of binary operations and comparisons on constrained type variables, ensuring the type variable is preserved when appropriate rather than degrading to a union of constraints.

Language Server

  • Literal value completions now work in more contexts. When assigning to an annotated variable, returning from a function, or setting an attribute with a Literal type, the editor now suggests the valid literal values.
  • New TSP endpoint typeServer/getExpectedType returns the contextually expected type at a cursor position (e.g., the parameter type for a call argument, the declared type for an assignment), enabling richer IDE features.
  • Improved "move module member" refactoring. When moving a symbol to another module, Pyrefly now rewrites consumer imports automatically, updating from source import foo to from target import foo across the codebase.
  • New "move symbol to new file" refactoring creates a new file for a top-level symbol, moves the definition, and updates all consumer imports in one action.
  • Enhanced pytest fixture support. Go-to-definition and find-references now work for pytest fixtures used as function parameters, navigating to the fixture definition.
  • Better handling of non-Python modules in build systems. Go-to-definition on imports from .thrift files and other non-Python modules now navigates to the module file when the specific symbol can't be resolved.

Coverage Reporting

  • New pyrefly coverage check command provides a user-friendly way to verify type coverage meets a threshold, with configurable output formats and fail-under percentage.
  • Coverage reports now exclude symbols that can't be imported due to shadowed namespace packages, providing more accurate coverage metrics.
  • Improved handling of stub re-exports. When a stub re-exports a class, the class's members are now correctly excluded from the coverage report to avoid inconsistent results.
  • Coverage reports now respect __all__ in stubs more accurately, only treating imports as public re-exports when they appear in __all__ or use the as alias syntax.

Error Reporting

  • Error output is now significantly faster (up to 75% reduction in printing time for large error counts) through optimized rendering and buffering.
  • New --output-format junit-xml option emits JUnit XML test reports, making it easier to integrate Pyrefly into CI dashboards.
  • Improved error messages for None-related type mismatches. When passing T | None where T is expected, the error now includes an actionable hint suggesting narrowing with is not None or widening the expected type.
  • Better error messages for missing overload matches, now including details about arity mismatches and specific argument type errors.

🐛 Bug fixes

We closed 24 bug issues this release 👏

  • #3554: Fixed false-positive unknown-name errors after short-circuit boolean operations. Code like if SOMETHING_DEFINITELY_FALSE and A: no longer reports A as unknown, since it's unreachable.
  • #3300: Fixed unknown-name false positive when a name is introduced via a walrus operator in a decorator. Names defined with := in decorator expressions are now visible after the decorated definition.
  • #1496, #3418, #3623: Fixed handling of defaults for function parameters with type variable annotations. Defaults like x: T = 0 are now validated correctly and used when solving type variables in calls.
  • #3059: Fixed __getitem__ resolution on type variables with constraints. Subscripting a type variable bounded by TypedDict or other subscriptable types now works correctly instead of falling back to object.__getitem__.
  • #3603: Fixed type narrowing for discriminated TypedDict unions when using membership tests. Expressions like event["ph"] in ("X", "C") now correctly narrow the union to matching members.
  • #3079, #3082: Fixed false-positive key errors after key in dict checks. When a TypedDict key is tested with in, subsequent subscript access no longer reports the key as possibly absent.
  • #3607: Fixed import resolution when using a config file. Bare imports like from bar import func that work at runtime now resolve correctly even when a pyrefly.toml is present, via the new enable-fallback-search-path option.
  • #357: Fixed unquoted forward reference handling in Python ≤3.13. Runtime-evaluated annotations now correctly report uninitialized forward names unless from __future__ import annotations is active.
  • #3536: Fixed invalid-variance error location for overloaded methods. The error now appears on the offending overload signature rather than always pointing to the first overload.
  • #3671: Fixed stack overflow when a descriptor's __get__ is itself a descriptor. Self-referential descriptor patterns now terminate gracefully instead of crashing.
  • And more! #3235, #3673, #3541, #3684, #3647, #3632, #3626, #3640, #3641, #3639, #3645, #3701, #3664, #3598

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==1.1.0-dev.2

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:

  1. pyrefly check --suppress-errors
  2. Run your code formatter of choice
  3. pyrefly check --remove-unused-ignores
  4. 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 Pyrefly documentation.


🖊️ Contributors this release

@rchen152, @stroxler, @kinto0, @yangdanny97, @connernilsen, @grievejia, @NathanTempest, @jorenham, @samwgoldman, @asukaminato0721, David Tolnay, @lolpack, @mikeleppane, @maggiemoss, @MarcoGorelli, @JakobDegen, @arthaud, Anqi Wu, @terror, @bigfootjon, @aahanaggarwal, @rchiodo, @magic-akari, @SamB, @nitishagar, @ndmitchell, @NarxPal, Gregory Carlin, @javabster, @thatfunkymunki, @shobhitmehro, @hrolfurgylfa


Please note: These release notes summarize major updates and features. For brevity, not all individual commits are listed.

Pyrefly v1.1.0-dev.1

Pyrefly v1.1.0-dev.1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 27 May 23:04

Release date: May 27, 2026

About dev releases
Dev releases (versions like X.Y.Z-dev.N) are non-stable snapshots cut periodically from trunk. They give early adopters a chance to try in-progress features and surface issues before the next stable release, but they don't carry the same stability or compatibility guarantees as a stable release — don't pin production projects to a dev version.

Pyrefly v1.1.0-dev.1 bundles 250 commits from 40 contributors.


✨ New & Improved

Type Checking

  • New incompatible-comparison diagnostic catches comparisons like int == str where operand types can't overlap.
  • Classes whose metaclass extends ABCMeta are now correctly treated as abstract.
  • Frozen dataclasses reject manual __setattr__/__delattr__ overrides.
  • Annotation-only descriptor fields are recognized as descriptors — fixes false positives for SQLAlchemy Mapped and similar asymmetric descriptor types.

Language Server

  • Code actions can convert dict literals to TypedDict, dataclass, or Pydantic model — with automatic imports.
  • Sphinx cross-references (:meth:, :class:, :func:) in docstrings now render as clickable links in hover tooltips.
  • Inlay hints for class attributes defined in __init__ without explicit annotations.
  • Supports python.analysis.diagnosticMode, python.analysis.importFormat, and python.analysis.inlayHints settings — full interop with the Python VS Code ecosystem.
  • Added support for legacy pkgutil-style namespace packages

Error Reporting

  • New explicit-any error kind (ignored by default) warns when Any appears in annotations or type alias bodies; includes migration support for mypy/pyright codebases.
  • Diagnostic paths in baseline.json are now relative and always use forward slashes — fixes baseline matching when CI checkout paths differ from local dev environments and across OSes.
  • The annotation-mismatch error kind has been removed (it was never emitted).

Configuration

  • New all preset enables every error kind at error severity — for codebases that want comprehensive checking. Available in both the CLI and the VS Code python.pyrefly.typeCheckingMode setting.
  • New pytorch-efficiency-lints flag turns on PyTorch efficiency checks at warn severity: catches .item() GPU sync, redundant .to(device), deprecated .cuda(), and print(tensor).

Tensor Shapes

  • Tensor shape operations now live in user-space stubs (torch/_shapes.pyi) via the new @uses_shape_dsl decorator.
  • DSL compile errors and shape-DSL type errors now emit proper diagnostics with precise source spans instead of panicking.
  • Recursive @shape_dsl_function definitions and invalid call signatures are caught at compile time.

Stubgen

  • Stubgen now emits synthesized __init__ for dataclasses, preserving constructor signatures in generated stubs.

Build & CI

  • Pyrefly now compiles on stable Rust — no more nightly toolchain dependency. GitHub CI workflows updated to match.
  • musllinux wheels are now built for Alpine and other musl-based distros.
  • Conformance test sources updated from upstream python/typing.

🐛 Bug fixes

We closed 34 bug issues this release 👏

  • #2798: Fixed false positive not-iterable error when iterating over a list stored in a dict that also contains non-iterable values. When a dict was built inside a loop with heterogeneous inner dicts (e.g., {"start": date, "tasks": []}), Pyrefly incorrectly inferred the inner dict's value type as date instead of date | list[...], causing spurious errors when accessing val["tasks"].
  • #3188: Fixed error suppression for multi-line implicit string concatenations. When a # pyrefly: ignore comment appeared above a multi-line implicit string concatenation, only the first error was covered. Pyrefly now reparses the AST to respect ignore comments for the entirety of the construct.
  • #3385: Fixed false positive missing-override-decorator when assigning to inherited properties. If a child class assigned to a property (with a setter) defined in a base class, Pyrefly incorrectly flagged it as an implicit override.
  • #3208: Fixed stubgen missing instance variables defined in __init__. Classes in generated stubs were missing attributes if those attributes were not explicitly annotated at the class level. Stubgen now emits synthesized __init__ for dataclasses, preserving constructor signatures.
  • #3237: Fixed cross-file references lost when CRLF/LF line endings differ. When files on disk used CRLF but the editor sent LF-normalized content via textDocument/didOpen, byte offsets diverged, causing exact byte-range comparisons to fail. Pyrefly now uses a line-number fallback to match definitions correctly.
  • #3378: Fixed exhaustive Enum variants not narrowing the type. When a Final Enum variant was checked with is not, the type was not narrowed out of the union, causing false positives in exhaustiveness checks.
  • #3413: Fixed strict mode insisting on @override for standard dunders. Pyrefly now skips missing-override-decorator for dunders inherited from object, as adding @override to __repr__, __eq__, etc., is pure noise.
  • #3455: Fixed crash when overload residual capture included PartialQuantified vars. The solver now correctly handles partial vars in overload residuals, preventing panics.
  • #3392: Fixed Self@[Enum] not being properly narrowed. For an exhaustive match on an enum type within an instance method, the self argument wasn't being narrowed as expected. Enum member subtraction now preserves and handles SelfType, allowing exhaustive enum match self fallbacks to narrow to Never.
  • #3299: Fixed incorrect type inference after __setitem__ / __getitem__. When a class's __setitem__ and __getitem__ signatures were asymmetric, Pyrefly incorrectly narrowed the assigned value. Subscript-assignment narrowing is now gated by symmetry checks, preventing false positives with custom container types.
  • And more! #3446, #3448, #3396, #1492, #2451, #3431, #3210, #3381, #2547, #3147, #3524, #3506, #3519, #3343, #3505, #3369, #3344, #3400, #3394, #3221, #3514, #3520, #3544, #3458

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==1.1.0-dev.1

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:

  1. pyrefly check --suppress-errors
  2. Run your code formatter of choice
  3. pyrefly check --remove-unused-ignores
  4. 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 Pyrefly documentation.


🖊️ Contributors this release

@stroxler, @rchen152, @ndmitchell, @yangdanny97, @kinto0, @jorenham, @asukaminato0721, @migeed-z, @samwgoldman, @lolpack, @grievejia, David Tolnay, @connernilsen, @arthaud, @maggiemoss, @NathanTempest, @f1sherFM, @mfish33, @lordhaa123, Anqi Wu, @javabster, @rexledesma, @MackDing, Brian Rosenfeld, @fylux, @YBJ0000, @arpitjain099, @EpicEric, @NarxPal, Philippe Bidinger, @knQzx, @yeetypete, @GHX5T-SOL, Tejesh Mehta, @fangyi-zhou, @LeSingh1, @P-r-e-m-i-u-m, @Arths17, @sjh9714, @mdbernard


Please note: These release notes summarize major updates and features. For brevity, not all individual commits are listed.

Pyrefly v1.0.0

Choose a tag to compare

@github-actions github-actions released this 12 May 20:13

Status: STABLE
Release date: 12 May 2026

Pyrefly v1.0.0 is here!

We're thrilled to announce that Pyrefly has reached its stable 1.0.0 release! Since our beta release in November 2025, we've fixed hundreds of bugs, improved performance, and added lots of new functionality. Pyrefly is already the default type checker for Instagram at Meta and has been adopted by other large production codebases like PyTorch and JAX. Today, we're making it official: Pyrefly is production ready.

This would not have been possible without our amazing open-source community. To everyone who filed GitHub issues, submitted pull requests, gave us feedback at conferences, or joined us on Discord: thank you. Your contributions shaped this release.

These release notes cover the major highlights since our beta release. For the full history, see our past weekly release notes.


Performance Improvements

We've continued to push Pyrefly's performance since the speed improvements we shared in February. Since beta:

  • 2–125x faster updated diagnostics after saving a file (no, that’s not a typo!). Thanks to fine-grained dependency tracking and streaming diagnostics, updates now consistently arrive in milliseconds
  • 20–36% faster full type checking on large projects like PyTorch and Pandas
  • 2–3x faster initial indexing when Pyrefly first scans your project
  • 40–60% less memory usage during both indexing and incremental type checking

(Tested on an M4 Macbook Pro using open-source benchmarks from type_coverage_py and ty_benchmark.)

Compare the performance of Pyrefly and other Python type checkers on our regularly updated benchmarking suite, which runs against 53 popular Python packages.


Configuration Presets

A new preset configuration option provides named bundles of error severities and behavior settings.

Preset Description
off Silences all diagnostics. Useful for IDE-only users or if you want total control of which errors are enabled.
basic Low-noise, high-confidence diagnostics only (syntax errors, missing imports, unknown names, etc.). Ideal for unconfigured projects or IDE-first users.
legacy For codebases migrating from mypy. Disables checks mypy doesn't have. pyrefly init now emits this preset automatically when migrating from a mypy config.
default The standard Pyrefly experience. Equivalent to having no preset.
strict Enables additional strict checks on top of the default preset. For users who want to avoid Any types in their codebase.

See the configuration docs for details.


Onboarding Experience

We’ve made improvements to the out-of-the-box experience for projects without a pyrefly.toml.

  • Automatic config synthesis — if you have a mypy or pyright config, Pyrefly automatically migrates your settings and synthesizes an appropriate in-memory Pyrefly config. (This is the same migration that pyrefly init would commit to disk.)
  • Basic preset for unconfigured projects — projects with no type checker config get the lightweight “basic” preset, which surfaces only high-confidence errors.
  • VS Code status bar — the status bar shows the active preset — e.g. Pyrefly (Basic) or Pyrefly (Legacy) — so you always know which mode is active.
  • Type error display settings — new VS Code settings let you control which preset applies to unconfigured files and suppress all diagnostics workspace-wide.

Type Checker Improvements

We've been hard at work making the type checker robust and feature-complete, with a focus on driving down false positives and improving type quality in real-world code bases. Here are some highlights:

  • Across the board we've eliminated many sources of false positives in enums, dataclasses, ParamSpec, descriptors, and more.
  • Support has been added for more type narrowing patterns, including preserving narrows in nested scopes and recognizing container membership checks.
  • Overload resolution was substantially reworked to handle more real-world patterns.
  • Pyrefly’s conformance to the Python typing specification has improved from 70% at beta to over 90% today.
  • We've added experimental support for tracking tensor dimensions through PyTorch models — see "What's Next" below.

LSP & IDE Improvements

  • We've added new refactoring capabilities like Safe Delete (with reference checking) and bulk source.fixAll.
  • Navigation is more precise, and hover cards surface richer information for imports, tuples, and NamedTuples.
  • Workspace mode is more stable, with multiple crash fixes and improved diagnostic publishing.

Framework & Notebook Support

  • Django — Pyrefly has improved support for model relationships, fields, and views, and understands factory_boy factories.
  • Pydantic — Pyrefly models Pydantic's runtime behavior more faithfully, with support for lax mode and range constraint validation, and handles more of the Pydantic ecosystem: RootModel, pydantic-settings, and pydantic.dataclasses.
  • Pytest integration — We've added Code Lens run buttons for test functions, as well as code actions to annotate fixture return types and parameters.
  • Jupyter notebooks — .ipynb IDE support has reached full parity with .py files, with rename, find references, code actions, and document symbols all supported.

Complementary Tooling

Pyrefly ships with tools to aid with adopting type checking in an existing codebase. Two new tools since beta:

  • pyrefly coverage report outputs a JSON report with annotation completeness and type completeness metrics per function, class, and module, so you can track coverage over time.
  • Baseline files let you snapshot current errors into a JSON file so only new errors are reported, as an alternative to inline suppression comments.

Updated Version Policy

Going forward, we’ll switch from a weekly to monthly cadence for minor (1.x.0) releases, with patch releases in between as-needed for critical fixes. We’ll continue providing release notes for minor versions, so you can see what’s new in each release.


What's Next

  • Tensor shape checking — Experimental support for tracking tensor dimensions through PyTorch models and catching shape mismatches statically. Learn more.
  • Pyrefly + AI agents — Pyrefly's speed makes it a natural verification step in agentic workflows. See our guide on adding Pyrefly to your agentic loop.
  • Continued improvements — We'll keep expanding library support, reducing false positives, and iterating on your feedback. Let us know what you need on GitHub or Discord.

Thank you to all our contributors!

The following people have directly contributed at least once to the development of Pyrefly since our first Alpha release.

@aahanaggarwal, @aaron-ang, @abdallhfattah, @Abel981, @abesto, @abhi-jha, @ABohra3, @Adamkaram, @Adist319, @adsi7698, @AHA705, @ahornby, @airvzxf, @ajaymiranda, @akmalsoliev, Alan Du, @Alex-Aron, Alok Priyadarshi, Alvaro Leiva Geisse, @AmalenduManoj, Anass Al-Wohoush, Anqi Wu, @ArchieBinnie, @arnav-jain1, @arosenber, @arthaud, @Arths17, @AryanBagade, @asm89, @asukaminato0721, @austin3dickey, @avikchaudhuri, Ben Carr, @bharath-2022, @bigfootjon, @bluetech, @bowiechen, @brchien, Brian Rosenfeld, @bv-saketha-rama, @capickett, Carlos Fernandez, @cbarrete, @cclauss, @charliecloudberry, @cjlongoria, Claudionor Santos, @connernilsen, @CookieComputing, @cooperlees, @cybardev, @DanielNoord, @danielocfb-test, @darricklaidin, David Tolnay, @davidbarsky, @ddrcoder, @dhleong, Dhruv Mongia, @diliop, @disrupted, @dluo, @Dogacel, @ducdetronquito, @ericweb2, @fangyi-zhou, @fannheyward, @fatelei, @github-main-user, @grantlouisherman, @grievejia, @gvozdvmozgu, @hanzel-sc, @hashiranhar, @hugovk, @iamPulakesh, @IDrokin117, @immanuel-peter, @Imran-S-heikh, @InSyncWithFoo, @ipr-ams, Ivan Loskutov, @j-piasecki, @jack-mcivor, @jackulau, @jagill, Jaimin Brahmbhatt, @JakobDegen, @javabster, @jchanke, Jess Wass, @jorenham, Jun Hao, @jvansch1, @K1T3K1, @KaranPradhan266, @Karman-singh15, Keito Uchiyama, @kinto0, @kitagry, @knQzx, @krathul, @krikera, @Krishnachaitanyakc, @kshitijgetsac, @kv9898, Li Shen, lianne, @lolpack, @Louisvranderick, @maggiemoss, @maifeeulasad, @maldoinc, @MarcoGorelli, @markmarkmarkthebest, @martindemello, @melvinhe, Miae Kim, @michaelcortese, @michel-slm, Mick Killianey, @migeed-z, Miles Conn, @mohesham88, Morgan Bartholomew, @MountainGod2, @mrsobakin, @mstykow, @mvanhorn, @NathanTempest, @ndmitchell, @nhawkes, @nikita-ashihmin, @nitinsingh-meta, @NSPC911, @ogios, @oopscompiled, @oriori1703, Owen Valentine, @oyarsa, @pavelzw, @pawelstrzmeta, @pawlowskialex, @PhilHem, @prasannavenkateshgit, @praskr-wisdom, @Prathamesh-tech-eng, @pswitchy, @pt2302, @QEDady, @QuantumManiac, @quark-zju, @Raf-Hs, @Rayahhhmed, @rchen152, @rchiodo, @regexyl, @rexledesma, @ricardoleal20, Robert Rusch, @robertoaloi, Ron Mordechai, @rubmary, @runlevel5, @salmanmkc, @salvatorebenedetto, @samcho...

Read more

Pyrefly v0.64.1

Choose a tag to compare

@github-actions github-actions released this 08 May 03:38

Full Changelog: 0.64.0...0.64.1

Pyrefly v0.64.0

Choose a tag to compare

@github-actions github-actions released this 06 May 17:29

Status : BETA
Release date: May 05, 2026

Pyrefly v0.64.0 bundles 190 commits from 20 contributors.


✨ New & Improved

Area What's new
Type Checking - You can now pass generic or overloaded callables to higher-order functions and Pyrefly will preserve their structure in the return type. For example, identity(identity) now correctly returns a generic callable instead of degrading to Unknown.

- Same-scope class rebinds (like Real = Dummy after class Real) are now checked against the original class as if it were an implicit type[Real] annotation, preventing silent type changes and fixing spurious constructor-call errors.

- Generic classes with missing type arguments in lax mode now default to Any instead of raising variance errors, improving consistency with how we handle other incomplete types.

- Pydantic field_validator decorators with mode='before' and mode='plain' are now supported, allowing validators to accept broader input types before coercion.

- Spurious unpack diagnostics are no longer emitted when the right-hand side involves Never (e.g. a, b, c = never() or a, b = (never(), 1)). The unpack solver is now Never-aware, recognizing that the producing expression cannot complete and any error message at the unpack site would be misleading.

- assert statements now check that __bool__ is callable on the test expression, matching the behavior already in place for if, while, and ternary expressions (and aligning with mypy and pyright).
Language Server - The language server now advertises both source.fixAll and source.fixAll.pyrefly code action kinds, enabling selective fix-on-save configuration across editors that implement the LSP protocol.

- Document highlights now correctly distinguish between read and write references, setting DocumentHighlightKind::WRITE for assignments and declarations.

- Go-to-definition on relative imports in site-packages files now correctly resolves to the package source instead of returning null when a pyproject.toml exists at the project root.

- Notebook cell index resolution has been fixed to prevent mismatches between code cells and markdown cells, eliminating panics and incorrect byte offset calculations in Jupyter notebooks.

- Cross-module "find references" (external references) is now enabled by default, returning references across the entire project rather than just the current file.

- A new quick fix turns the existing "Did you mean Foo.BAR?" diagnostic note for missing enum members into a code action that replaces the offending string literal with the proper enum member access.

- A new # pyrefly: ignore quick fix inserts a suppression comment for the diagnostic at the cursor, automatically merging into an existing pyrefly-ignore directive on the same line or on a comment-only line above when present.

- Numeric parameter defaults now preserve their source spelling (e.g. 0o777, 0xFF, 0b101) in hover and signature display rather than being normalized to decimal.

- Code actions documentation has been added to the IDE Supported Features page, covering quick fixes and source.fixAll.pyrefly configuration.
Onboarding & VS Code Extension - A redesigned unconfigured-project experience: when no pyrefly.toml is found, Pyrefly auto-detects nearby mypy.ini, pyrightconfig.json, or [tool.mypy]/[tool.pyright] sections in pyproject.toml and synthesizes an in-memory configuration migrated from those settings (using the legacy or default preset respectively). With no detectable configuration, the new basic preset is used.

- A new python.pyrefly.typeCheckingMode workspace setting (auto / off / basic / legacy / default / strict, default auto) lets users pick a preset for files not covered by an explicit Pyrefly configuration, directly from the VS Code settings UI. The legacy python.pyrefly.displayTypeErrors setting is now deprecated, with values transparently mapped to the new model.

- A new python.pyrefly.disableTypeErrors workspace setting provides a clean per-workspace kill switch for diagnostics, independent of the type-checking mode.

- The VS Code status bar has been redesigned: it now shows the active preset (e.g. "Pyrefly (Legacy)", "Pyrefly (Basic)") and the tooltip explains why that preset was chosen and links to the relevant docs.

- After a pyrefly check on an unconfigured project, the CLI now prints a short upsell to stderr explaining what configuration was synthesized and pointing at pyrefly init. The message is routed to stderr so machine-readable stdout formats (e.g. --output-format json) remain untouched.
Configuration - Configuration presets (off, basic, legacy, default, strict) are now available via the preset option, providing named collections of error severities and behavior settings as a base configuration that user settings can override.

- The legacy preset is now used by pyrefly init for mypy migration, disabling checks mypy doesn't have and setting looser inference defaults.

- The implicit-any error code has been split into sub-kinds (implicit-any-attribute, implicit-any-empty-container, implicit-any-parameter, implicit-any-type-argument) with implicit-any as the parent, allowing finer-grained control over where implicit Any is flagged.

- The unbound-name error is now disabled in the legacy preset to match mypy's default behavior, which does not flag possibly-undefined variables.
Error Reporting - A new incompatible-overload-residual error kind has been introduced for cases where all branches of an overloaded callable are pruned during higher-order function analysis, making it easier to configure these errors independently.

- Error messages for all-pruned overload residuals now describe the incompatibility in terms of "solved type variables" rather than "solved type constraints" for better clarity.

- The pyrefly suppress command now correctly handles removal of unused ignores via the --remove-unused flag, which was previously broken.
Factory Boy Support - Pyrefly now infers the correct model return types for create(), build(), create_batch(), and build_batch() methods on DjangoModelFactory subclasses by reading the inner Meta.model attribute.

- False-positive bad-override errors on the inner Meta class in factory-boy factories are now suppressed, matching how we handle Django and Marshmallow.
Reporting - The pyrefly report JSON output now includes a path field on each ModuleReport, for compatibility with typestats and similar tooling.
Performance - Deeply-nested dict literals no longer cause exponential memory growth during type inference. A depth-25 dict literal that previously consumed ~7.7 GB now uses ~239 MB by computing the union of field types on demand instead of storing it redundantly.

- Callable residual finalization has been optimized to avoid redundant type cloning and traversals, reducing memory churn in attribute-heavy code.

- Eliminated some bugs that caused Pyrefly to unnecessarily analyze dependencies, improving latency and memory use, especially in the IDE.

🐛 bug fixes

We closed 15 bug issues this release 👏

  • #3057: Fixed an issue where string concatenation with the + operator was incorrectly flagging str as not assignable to LiteralString attributes. Pyrefly now preserves LiteralString style when adding two explicit string literals and uses implicit style otherwise.
  • #105: Fixed premature type pinning in function calls where arguments were incorrectly narrowed before all constraints were solved. For example, foo(x, y) with x: int | None and y: int | None no longer incorrectly narrows x to None when passed to a generic foo[T](a: T, b: T).
  • #3198: Fixed pyrefly suppress --remove-unused which was not actually removing unused error suppressions. The command now correctly processes the --remove-unused flag.
  • #3024: The language server now advertises source.fixAll.pyrefly in addition to source.fixAll, allowing users to selectively enable or disable Pyrefly's fix-all actions in editors that support LSP code action kinds.
  • #2819: Fixed incorrect variance errors when using generic classes like Pydantic's RootModel in lax mode. Missing type arguments now degrade to Any instead of raising errors, matching our handling of other incomplete types.
  • #3000: Fixed "find references" failures in Cursor and other editors caused by relative imports in site-packages not resolving correctly when a pyproject.toml existed at the project root.
  • #2563: Fixed go-to-definition on relative imports in virtual environment site-packages, which was returning null because the project root's import path was matching before the more specific site-package prefix.
  • #3193: Fixed an error where list["A|B"] was incorrectly rejected as not-a-type. Type argument subscripts are now bound as type expressions even in value context, allowing forward-ref strings to be parsed.
  • #3286: Fixed exponential memory blowup when type-checking deeply-nested dict literals, which could cause VSCode to be killed by the OS. Memory usage for a depth-25 dict dropped from ~7.7 GB to ~239 MB.
  • #3261: Fixed a false positive bad-class-definition when a dataclass field was assigned inside a @classmethod or __init_subclass__. Pyrefly was incorrectly extracting these as dataclass fields, even though Python's dataclasses.dataclass ignores them at runtime.
  • #2914: assert statements now flag a non-callable __bool__ on the test expression, closing a gap that previously only caught the issue inside if, while, and ternary expressions.
  • #286...
Read more

Pyrefly v0.63.1

Choose a tag to compare

@github-actions github-actions released this 29 Apr 06:00

Full Changelog: 0.63.0...0.63.1

Pyrefly v0.63.0

Choose a tag to compare

@github-actions github-actions released this 27 Apr 21:45

Status : BETA
Release date: April 27, 2026

Pyrefly v0.63.0 bundles 129 commits from 26 contributors.


✨ New & Improved

Area What's new
Type Checking - Enum member types are preserved even when the metaclass conflicts with EnumMeta, reducing noise in projects using custom metaclasses with enums.

- Constrained TypeVars no longer get pinned to a specific constraint when matched against Any, preventing false positives.

- Self/cls annotations on all methods and classmethods are validated to ensure they reference the defining class or a superclass, catching more annotation errors.
Language Server - The LSP now reports unused-ignore diagnostics when configured to do so, helping you clean up stale suppression comments.

- Completions for attribute override definitions are available in class bodies, surfacing base-class members filtered by fuzzy match.

- The LSP server no longer crashes on Jupyter notebook cell URIs (vscode-notebook-cell:), with full support for resolving notebook cell paths and position offsets.

- Workspace symbol search uses the correct location for re-exported symbols, preventing panics on multi-byte UTF-8 characters.

- Inlay hints are clickable for built-in types like tuple, dict, and str, enabling go-to-definition directly from hint overlays.
Error Messages - A new unnecessary-type-conversion lint warns when str(), int(), or float() is called on an argument that is already of that exact type.
Reporting & Coverage - Public symbol filtering is available via pyrefly report --public-only, using cross-module tracing to report only public symbols.
Performance - TypedDict subset checks are now cached on the Solver, reducing CPU time by ~5.3x and wall time by ~6.7x on pydantic (from 9.5s to 1.4s).
Configuration & Initialization - pyrefly init supports --dry-run for safe previews without writing files, and --print-config for machine-readable TOML output.

🐛 bug fixes

We closed 9 bug issues this release 👏

  • #3099: Fixed an issue where property setters and deleters inflated typable counts in pyrefly report by incorrectly counting their trivial -> None return types.
  • #3098: Fixed an issue where overloads in pyrefly report were not deduplicated, causing parameters and callable signatures to be counted multiple times and inflate coverage metrics.
  • #3067: Fixed an issue where the type display path was dropping the unpack marker (*) for direct TypeVarTuple arguments, causing Shape to render bare instead of *Shape.
  • #3040: Fixed an issue where properties on metaclasses were not taking precedence over properties on the class during class-level attribute access, causing false bad-assignment and bad-return errors.
  • #3150: Fixed an issue where type aliases were inflating type coverage in pyrefly report by being counted as typable entities.
  • #3041: Fixed a panic during workspace/symbol requests on re-exported symbols with multi-byte UTF-8 characters, caused by using the canonical module's byte offset against the re-exporting file's buffer.
  • #3109: Added a new unnecessary-type-conversion lint that warns when str(), int(), or float() is called on an argument that is already of that exact type, making the conversion redundant.
  • #3187: Fixed a panic in pyrefly report when @no_type_check decorator was used, caused by a missing key lookup for skipped parameter annotations.
  • #3090: Improved the unused-coroutine error message when an await expression already has await but produces a coroutine due to an incorrect return type annotation on the function definition.

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==0.63.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:

1. pyrefly check --suppress-errors
2. run your code formatter of choice
3. pyrefly check --remove-unused-ignores
4. 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 Pyrefly documentation


🖊️ Contributors this release

@rchen152, @migeed-z, @avikchaudhuri, @grievejia, @kinto0, @jorenham, @jvansch1, generatedunixname2066905484085733, @stroxler, @tejasreddyvepala, David Tolnay, @fangyi-zhou, @asukaminato0721, @lolpack, @NathanTempest, @connernilsen, @zbowling, @rubmary, @rexledesma, Anass Al-Wohoush, @javabster, @ABohra3, generatedunixname89002005232357, @tkaleas, @knQzx, generatedunixname89002005307016


Please note: These release notes summarize major updates and features. For brevity, not all individual commits are listed. Highlights from patch release changes that were shipped after the previous minor release are incorporated here as well.

Pyrefly v0.62.0

Choose a tag to compare

@github-actions github-actions released this 20 Apr 17:13

Status : BETA
Release date: April 20, 2026

Pyrefly v0.62.0 bundles 87 commits from 23 contributors.


✨ New & Improved

Area What's new
Type Checking - TypeVarTuple inference has been changed to be consistent with TypeVar, per a recent change to the typing spec.

- Errors logged during speculative union checks and overload calls are now reverted, eliminating a source of confusing false positives.

- Union-typed decorators that return fully unknown types (either Unknown or callables with all-unknown signatures) preserve the original function signature instead of replacing it with Unknown, reducing false positives by ~23% on TensorFlow.
Language Server - Semantic tokens and completions work for inmemory:// documents on Windows.

- LSP server crashes from out-of-range line numbers in client requests are prevented by clamping positions to the buffer's valid range.
Error Reporting - Error kinds can now have sub-kinds that can be disabled using their shared prefix.

- Invariance checks for mutable attributes (corresponding to mypy's mutable-override opt-in behavior) have been moved to a new bad-override-mutable-attribute error code that is a sub-kind of bad-override.

- The bad-param-name-override error has been renamed to bad-override-param-name and made a sub-kind of bad-override.

- Sub-configs that define [errors] inherit the root config's error severity overrides for any codes they don't explicitly set.
Configuration - When migrating from mypy via pyrefly init, bad-override-mutable-attribute is disabled by default to match mypy's behavior.

- Project excludes (e.g., project-excludes = ["**/*.ipynb"]) no longer block discovery of .py files when the default project-includes contains both **/*.py* and **/*.ipynb.

🐛 bug fixes

We closed 12 bug issues this release 👏

  • #3118: Fixed incorrect stub package recommendations for typeshed third-party libraries. Pyrefly now suggests the correct package name (e.g., types-python-dateutil for the dateutil module, not types-dateutil) by extracting the module→package mapping from the bundled typeshed archive, preventing potential typosquatting.
  • #3081: Fixed NewType wrappers with NoneType bases being incorrectly rejected or treated inconsistently. NewType("NewNoneType", NoneType) is now accepted as a valid nominal type declaration, and plain None is correctly rejected where NewNoneType is required.
  • #3052: Fixed false positive unexpected-keyword errors for named parameters before *args: P.args. Functions like call_with_retry(f, max_attempts=10, *args: P.args, **kwargs: P.kwargs) now correctly allow max_attempts to be passed as a keyword argument, matching mypy and pyright behavior.
  • #3110: Fixed LSP server crashes when the client sends a position with a line number beyond the end of the buffer (e.g., after a DidChangeTextDocument race where the file was truncated). Out-of-range positions now map to EOF instead of panicking.
  • #2912: Fixed false positive bad-argument-type for list(null_values.items()) when the return type hint is a union like Sequence[str] | list[tuple[str, str]]. Pyrefly now tries constructing the class with each union member independently and unions the results, ensuring the inferred type is assignable to the hint.
  • #2644: Fixed false positive bad-argument-type when calling a method with AnyStr. Placeholder variables used during overload resolution are now saved and restored around overload calls, preventing AnyStr from being incorrectly specialized to str and polluting subsequent checks.
  • #2872: Fixed false positive invalid-type-var for generic functions captured as closure default arguments. The Visit implementation for DefaultValue now calls visit instead of recurse, ensuring type-level visitors see the Type node stored in the default value.
  • #3159: Fixed incorrect type inference for .value on enum members with non-data-type mixins. Mixins that don't define __new__ (e.g., class Meta: pass) are no longer treated as data type mixins, so Foo.bar.value correctly returns Literal[1] instead of Meta.
  • #3161: Fixed false positive bad-argument-type for overloaded functions with vararg unpacking (e.g., *args: *tuple[int, str]). Type check errors for unpacked varargs are now sent to call_errors instead of arg_errors, so they don't cause the overload to be incorrectly rejected.
  • #3047: Fixed false positive bad-specialization when matching a type variable against a union like N | Iterable[N]. Pyrefly now uses snapshot-based rollback when trying each union member, ensuring specialization errors from one branch don't leak into the final result if another branch succeeds without errors.
  • And more! #3122, #3080, #3074

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==0.62.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:

1. pyrefly check --suppress-errors
2. run your code formatter of choice
3. pyrefly check --remove-unused-ignores
4. 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 Pyrefly documentation


🖊️ Contributors this release

@rchen152, @stroxler, @migeed-z, @jorenham, @samwgoldman, @connernilsen, @NathanTempest, @kinto0, @jvansch1, @fangyi-zhou, @tejasreddyvepala, David Tolnay, generatedunixname2066905484085733, @mstykow, @AHA705, @Arths17, @grievejia, Claudionor Santos, @austin3dickey, @robertoaloi, @salvatorebenedetto, @iamPulakesh, generatedunixname89002005307016


Please note: These release notes summarize major updates and features. For brevity, not all individual commits are listed. Highlights from patch release changes that were shipped after the previous minor release are incorporated here as well.