Bump pyrefly from 0.60.0 to 0.61.1 in /backend

[dependabot]

Bumps pyrefly from 0.60.0 to 0.61.1.

Release notes

Sourced from pyrefly's releases.

Pyrefly v0.61.1

Full Changelog: facebook/pyrefly@0.61.0...0.61.1

Pyrefly v0.61.0

Status : BETA Release date: April 13, 2026

Pyrefly v0.61.0 bundles 85 commits from 21 contributors.

---

✨ New & Improved

Area	What's new
Type Checking	- Division, floor division, and modulo operations with a literal zero divisor (e.g., x / 0, y // 0, z % 0) are flagged as errors, catching runtime ZeroDivisionError before execution. - Multiple inheritance with conflicting __slots__ definitions is detected and reported as an error, matching CPython's runtime behavior and preventing layout conflicts. - Protocol members assigned a value without an explicit type annotation (e.g., x = None in a Protocol class body) are flagged as errors, ensuring protocol members have declared types as required by the typing specification.
Language Server	- Variables used exclusively within f-string format specifiers (e.g., f"{key:<{max_len}}") are correctly recognized as used, eliminating false positive unused-variable warnings. - The VS Code extension explicitly declares workspace trust capabilities, requiring trusted workspaces to run and allowing machine-overridable scope for lspPath and lspArguments settings for improved security.
Coverage Reporting	- The pyrefly report command now excludes some dunder methods and typing-only constructs from coverage metrics. - Per-module JSON output includes entity counts (n_functions, n_methods, n_function_params, n_method_params, n_classes, n_attrs, n_properties, n_type_ignores) for downstream consumers. - A new --module <name> CLI flag allows overriding the module name in JSON output, supporting callers that need canonical package names instead of filesystem-derived names.
Pydantic	- Pydantic lax conversion special-cases regex patterns, fixing false positives when passing compiled patterns to Pydantic models.
Performance	- Fixed a bug in overload evaluation that caused exponential memory consumption and indefinite hangs on code with many overloaded calls.

---

🐛 bug fixes

We closed 9 bug issues this release 👏

• #3031: Fixed a crash in mypy_primer caused by a variable leak in LitEnum — types are now deep-forced before storage to prevent leaking vars into the solver.
• #2915: Division, floor division, and modulo by literal 0 are now flagged as errors, catching ZeroDivisionError at static analysis time instead of runtime.
• #3009: Fixed false positive unused-variable warnings for variables used exclusively within f-string format specifiers (e.g., f"{key:<{max_len}}"). The AST visitor now correctly descends into format_spec nodes.
• #2799: Fixed false positive [missing-attribute] errors for dict.setdefault(key, []).append(val) on unannotated dicts. Overload resolution now creates fresh partial variables for each overload, preventing incorrect pinning.
• #2991: Fixed Pydantic lax-mode rewriting re.Pattern[str] to Pattern[LaxStr] and rejecting re.Pattern[str]. Regex patterns now expand to re.Pattern[T] | T instead of recursively widening the inner type.
• #2916: Fixed runtime TypeError from multiple inheritance with conflicting __slots__ (same slot names). Pyrefly now detects and reports this layout conflict during class metadata computation.
• #2917: Fixed runtime TypeError from multiple inheritance with conflicting __slots__ (different slot names). Pyrefly now detects non-empty __slots__ in multiple bases and reports the conflict.
• #3064: Fixed false positive when using issubclass() after isinstance() narrowing with custom metaclasses (e.g., Django's ModelBase). Metaclass instances are now correctly accepted as valid class objects.
• #3030: Fixed false positive LiteralString type error in map(str.strip, ...). Overloads with narrower self-type annotations are now filtered out during unbound method resolution.

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.61.0

How to safely upgrade your codebase

... (truncated)

Commits

• 582ad83 Bump Pyrefly version to 0.61.1
• b71ef04 Bump icu_decimal 2.1.1 -> 2.2.0
• 526415a Update vendored wasm-bindgen to 0.2.118
• 2335601 Keep specialization errors arising from hints to overloaded calls
• 73b8f63 Use with_snapshot for is_subset_eq on unions
• ce37688 Take instantiation errors into account in Subset::with_snapshot
• e2e3874 Add Solver::has_new_instantiation_errors
• 251ccae Check for key in instantiation_errors before removing it
• 2d69b92 Reduce code repetition in is_subset_eq union case
• 2f6fa7a Restore var state after failed Quantified checks in is_subset_eq
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[cloudflare-workers-and-pages]

Deploying bracket-docs with    Cloudflare Pages

Latest commit:	090a700
Status:	⚡️  Build in progress...

View logs