deps: Update dependency pyrefly to v1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
pyrefly (source)	feature-lint	major	>=0.63.1,<0.64 → >=1.0.0,<1.1

---

Release Notes

facebook/pyrefly (pyrefly)

v1.0.0: Pyrefly v1.0.0

Compare Source

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, @​SamChou19815, @​samwgoldman, @​sandeshbhusal, @​sargun, @​Sehat1137, @​self-sasi, @​serephus, @​sgavriil01, @​shayne-fletcher, @​shining44, @​ship-it-ship-it, @​shuv-amp, @​sifex, @​simonhollis, @​singiamtel, @​ska-kialo, @​slawlor, @​Solumin, @​stanleyshen2003, @​stroxler, Takuma Iwaki, @​Tamchuk, @​tannguyencse19, @​tejasreddyvepala, @​terror, @​TheRustyPickle, @​thomaspolasek, Tianhan Lu, @​tkaleas, @​tsembp, @​ukautz, @​Viicos, @​vinnymeller, Vladimir Matveev, Weixi Ma, @​Wilfred, Will Li, @​willylau, @​xaskii, @​xl4624, @​yamgent, @​yangdanny97, @​yeetypete, @​yslim-030622, @​zachmullen, @​zanieb, @​zbowling, @​Zeko369, @​zertosh, @​zhuolix, @​zpao, @​zriser, @​zsol

v0.64.1: Pyrefly v0.64.1

Compare Source

Full Changelog: facebook/pyrefly@0.64.0...0.64.1

v0.64.0: Pyrefly v0.64.0

Compare Source

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.
• #​2867: Fixed urlunparse being inferred as returning Literal[b''] instead of str. The fix reworks as_superclass so tuple-like NamedTuple subclasses are upcast through their erased tuple element types, which stops ParseResult from spuriously matching Iterable[None] and selecting the bytes overload.
• #​3266: Added a quick fix for the existing "Did you mean Foo.BAR?" diagnostic note for missing enum members, turning the suggestion into a code action that rewrites the surrounding string literal.
• #​3230: Numeric parameter defaults now preserve their original spelling (e.g. 0o777) in hover and signature display rather than being normalized to a decimal value.
• #​3302: Added a path field to the pyrefly report JSON ModuleReport, restoring compatibility with typestats.

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.64.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 [Pyefly documentation](https://pyrefly.org/en/docs/error-suppressions/)

---

🖊️ Contributors this release

@​stroxler, @​rchen152, @​migeed-z, @​grievejia, @​samwgoldman, @​kinto0, @​asukaminato0721, @​jvansch1, @​NathanTempest, @​avikchaudhuri, @​connernilsen, Carlos Fernandez, David Tolnay, @​jorenham, @​rexledesma, @​arthaud, @​pawlowskialex, @​QuantumManiac, @​knQzx, @​QEDady

---

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.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[lucascolley]

hat tip @MarcoGorelli