Bump pyrefly from 0.29.1 to 0.33.1

[dependabot]

Bumps pyrefly from 0.29.1 to 0.33.1.

Release notes

Sourced from pyrefly's releases.

Pyrefly v0.33.0

Status : ALPHA
Release date: 15 September 2025

Pyrefly v0.33.0 bundles 117 commits from 21 contributors

---

✨ New & Improved

Area	What’s new
Type Checker Behavior	- Pyrefly now distinguishes between Any as a value and as a type, preventing incorrect attribute access and constructor calls on Any values. For example, when Any (the value) is used as an attribute base or call target pyrefly will now error if you try to access attributes that are not defined on type. - Basic support added for TypeAliasType Experimental support for Pydantic now available! - Type error messages by default now print paths relative to working directory (as opposed to absolute path)
IDE improvements	- Kwarg completion now supports literals and unions of literals (requested feature) - A new "typeServer/getSupportedProtocol" request handler included to fetch TSP version information
Website and Documentation	- The sandbox feature on the website has been upgraded! It can now deal with multiple files, allowing users to try out Pyrefly with cross-file imports. Give it a go here! - New documentation guide on experimental Pydantic support, read it here - New editable installs section in documentation, detailing the nuances of working with editable dependencies. Read it here.

---

🐛 Bug fixes

We closed 4 bug issues this release 👏

• #1052 - regression that caused issue with return type list[Self]
• #1034 - Python version dropdown in website sandbox not working properly
• #817 - bad-override error split into 2 separate error codes for type and name differences in arguments
• #573 - when a package is pip-installed as editable from a local directory as a dependency, it was added in a way that Pyrefly didn’t recognise

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.33.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/)

... (truncated)

Commits

• f1b3475 Bump to 0.33.1 (#1113)
• 707ba27 Add max files arg for dump config
• 81133d9 Add nesting context to Class::has_qname()
• 1f9ba6f Use nesting context to print nested class names properly
• 67fcf91 Pass around nesting context to answer solver
• d644589 Pass around nesting context in binding builder
• 4e3ba0b Introducing a NestingContext data structure to represent nestings properly
• 41d50a3 Move QName from pyrefly_types to pyrefly_python
• 82e59ae Rename loc to range
• 168859b Add del-defined names to Definitions
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[dependabot]

Superseded by #172.