Bumps [pyrefly](https://github.com/facebook/pyrefly) from 0.56.0 to 0.57.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/facebook/pyrefly/releases">pyrefly's releases</a>.</em></p> <blockquote> <h2>Pyrefly v0.57.1</h2> <p>Fixed a bug that could cause Pyrefly to hang.</p> <h2>Pyrefly v0.57.0</h2> <p><strong>Status: Beta</strong><br /> <em>Release date: March 16, 2026</em></p> <p>Pyrefly 0.57.0 bundles <strong>116 commits</strong> from <strong>17 contributors</strong>.</p> <hr /> <h2>✨ New & Improved</h2> <table> <thead> <tr> <th align="left">Area</th> <th align="left">What’s new</th> </tr> </thead> <tbody> <tr> <td align="left"><strong>Type Checking</strong></td> <td align="left">- Improved type narrowing for <code>hasattr</code> inside loops <!-- raw HTML omitted --><!-- raw HTML omitted -->- <code>pyrefly suppress</code> no longer corrupts multiline f-strings/t-strings by inserting suppression comments inside the string; it now places comments above the string and also matches suppressions correctly for errors inside multiline f/t-strings <!-- raw HTML omitted --><!-- raw HTML omitted -->- Improved <code>namedtuple</code> support with <code>*</code> field unpacking <!-- raw HTML omitted --><!-- raw HTML omitted -->- Fewer false-positive “variable is not initialized” errors</td> </tr> <tr> <td align="left"><strong>Language Server</strong></td> <td align="left">- if a nested pyproject.toml contains <code>[tool.ruff]</code> / <code>[tool.mypy]</code> / <code>[tool.pyright]</code>, it’s treated as a strong “this is a Python project root” marker, preventing parent pyrefly.toml from incorrectly shadowing it (notably improving go-to-def accuracy on some repos)</td> </tr> <tr> <td align="left"><strong>Performance</strong></td> <td align="left">- Typechecking speed has improved, making it now ~20% faster to type check Pytorch on recent benchmarks</td> </tr> </tbody> </table> <hr /> <h2>🐛 bug fixes</h2> <p>We closed 24 bug issues this release 👏</p> <ul> <li><a href="https://redirect.github.com/facebook/pyrefly/issues/2696">#2696</a>: Fixed an issue where Pyrefly’s LSP incorrectly flagged <code>from typing import NewType</code> as unused, even when <code>NewType(...)</code> was referenced.</li> <li><a href="https://redirect.github.com/facebook/pyrefly/issues/2743">#2743</a>: Fixed an issue where <code>TypedDict</code> fields named items/values prevented access to the corresponding <code>dict.items()</code> / <code>dict.values()</code> methods via attribute lookup.</li> <li><a href="https://redirect.github.com/facebook/pyrefly/issues/2745">#2745</a>: Fixed an issue where chained/nested narrowing expressions (e.g. multi-clause and conditions) failed to narrow correctly when using negative subscript indices.</li> <li><a href="https://redirect.github.com/facebook/pyrefly/issues/2737">#2737</a>: Fixed an issue where <code>functools.partial(...)</code> results couldn’t be assigned back to a Callable typed with a <code>ParamSpec</code>, causing a false-positive type error.</li> <li><a href="https://redirect.github.com/facebook/pyrefly/issues/2650">#2650</a>: Fixed an issue where a <code>Protocol</code> parameterized by <code>ParamSpec[...]</code> wasn’t considered compatible with an equivalent “gradual” protocol using <code>*args: Any, **kwargs: Any</code>.</li> <li><a href="https://redirect.github.com/facebook/pyrefly/issues/2334">#2334</a>: Fixed an issue where calling <code>__init__</code> on parametrized bound methods could trigger a false-positive type error due to incorrect attribute lookup behavior.</li> <li><a href="https://redirect.github.com/facebook/pyrefly/issues/2731">#2731</a>: Fixed an issue where <code>super()</code> calls to abstract methods that do have a concrete runtime body were incorrectly reported as missing-attribute / abstract-call errors.</li> <li><a href="https://redirect.github.com/facebook/pyrefly/issues/828">#828</a>: Fixed an issue where reading a conditionally-initialized variable didn’t “commit” the initialization, leading to redundant follow-on “may be uninitialized” errors.</li> <li><a href="https://redirect.github.com/facebook/pyrefly/issues/835">#835</a>: Fixed an issue where type information for subclasses wasn’t handled correctly, leading to failures when type-checking subclass relationships.</li> <li>And more! <a href="https://redirect.github.com/facebook/pyrefly/issues/2522">#2522</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1800">#1800</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/2736">#2736</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/2382">#2382</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/913">#913</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1397">#1397</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/2261">#2261</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/2669">#2669</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/2744">#2744</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/2739">#2739</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1575">#1575</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/903">#903</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1043">#1043</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1429">#1429</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/2607">#2607</a></li> </ul> <p>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 <a href="https://github.com/facebook/pyrefly/issues">here</a></p> <hr /> <h2>📦 Upgrade</h2> <pre lang="shell"><code>pip install --upgrade pyrefly==0.57.0 </code></pre> <h3>How to safely upgrade your codebase</h3> <p>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:</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="9d24c65115"><code>9d24c65</code></a> v0.57.1</li> <li><a href="0c8881eee7"><code>0c8881e</code></a> Fix infinite loop in variance inference for self-referential generic classes</li> <li><a href="12e59d0b05"><code>12e59d0</code></a> Reviewed By: rchen152</li> <li><a href="e02d9948c8"><code>e02d994</code></a> Wire up Glean external references for incoming call hierarchy</li> <li><a href="3c5feafbce"><code>3c5feaf</code></a> Add convert_external_references_to_incoming_calls</li> <li><a href="8524405b36"><code>8524405</code></a> add "why you should use pyrefly" FAQ</li> <li><a href="753c5a369a"><code>753c5a3</code></a> Add PysaModuleIndex to replace cross-module ModuleContext::create calls</li> <li><a href="651f4984b0"><code>651f498</code></a> Optimise comment parsing</li> <li><a href="372fe49ab0"><code>372fe49</code></a> Remove unused code in the pyrefly_util crate</li> <li><a href="1998c105e6"><code>1998c10</code></a> Remove unused code in the pyrefly_bundled crate</li> <li>Additional commits viewable in <a href="https://github.com/facebook/pyrefly/compare/0.56.0...0.57.1">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Demo · Documentation · Quickstart · GitHub · Releases
Tournament system meant to be easy to use. Bracket is written in async Python (with FastAPI) and Vite as frontend using the Mantine library.
It has the following features:
- Supports single elimination, round-robin and swiss formats.
- Build your tournament structure with multiple stages that can have multiple groups/brackets in them.
- Drag-and-drop matches to different courts or reschedule them to another start time.
- Various dashboard pages are available that can be presented to the public, customized with a logo.
- Create/update teams, and add players to teams.
- Create multiple clubs, with multiple tournaments per club.
- Swiss tournaments can be handled dynamically, with automatic scheduling of matches.
Live Demo
A demo is available for free at https://www.bracketapp.nl/demo. The demo lasts for 30 minutes, after which your data will de deleted.
Quickstart
To quickly run bracket to see how it works, clone it and run docker compose up:
git clone git@github.com:evroon/bracket.git
cd bracket
sudo docker compose up -d
This will start the backend and frontend of Bracket, as well as a postgres instance. You should now be able to view bracket at http://localhost:3000. You can log in with the following credentials:
- Username:
test@example.org - Password:
aeGhoe1ahng2Aezai0Dei6Aih6dieHoo.
To insert dummy rows into the database, run:
docker exec bracket-backend uv run --no-dev ./cli.py create-dev-db
See also the quickstart docs.
Usage
Read the usage guide for how to organize a tournament in Bracket from start to finish.
Configuration
Read the configuration docs for how to configure Bracket.
Bracket's backend is configured using .env files (prod.env for production, dev.env for development etc.).
But you can also configure Bracket using environment variables directly, for example by specifying them in the docker-compose.yml.
The frontend doesn't can be configured by environment variables as well, as well as .env files using Vite's way of loading environment variables.
Running Bracket in production
Read the deployment docs for how to deploy Bracket and run it in production.
Bracket can be run in Docker or by itself (using uv and pnpm).
Development setup
Read the development docs for how to run Bracket for development.
Prerequisites are pnpm, postgresql and uv to run the frontend, database and backend.
Translations
Based on your browser settings, your language should be automatically detected and loaded. For now, there's no manual way of choosing a different language.
Supported Languages
To add/refine translations, Crowdin is used. See the docs for more information.
More screenshots
Help
If you're having trouble getting Bracket up and running, or have a question about usage or configuration, feel free to ask. The best place to do this is by creating a Discussion.
Supporting Bracket
If you're using Bracket and would like to help support its development, that would be greatly appreciated!
Several areas that we need a bit of help with at the moment are:
- ⭐ Star Bracket on GitHub
- 🌐 Translating: Help make Bracket available to non-native English speakers by adding your language (via crowdin)
- 📣 Spread the word by sharing Bracket to help new users discover it
- 🖥️ Submit a PR to add a new feature, fix a bug, extend/update the docs or something else
See the contribution docs for more information on how to contribute
Contributors
|
Erik Vroon |
Null |
BachErik |
Danny Piper |
Max Ricketts-Uy |
Sevi C |
|
Nicolas Vanheuverzwijn |
Amin NAIRI |
Felipe Gomes De Melo |
IzStriker |
Jon Miller |
Oscar Tobar Rios |
|
Raphael Le Goaller |
License
Bracket is licensed under AGPL-v3.0.
Please note that any contributions also fall under this license.
See LICENSE



