Bumps [pyrefly](https://github.com/facebook/pyrefly) from 0.64.1 to 1.0.0. <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 v1.0.0</h2> <p><strong>Status: STABLE</strong> <em>Release date: 12 May 2026</em></p> <h2>Pyrefly v1.0.0 is here!</h2> <p>We're thrilled to announce that Pyrefly has reached its stable 1.0.0 release! Since our <a href="https://github.com/facebook/pyrefly/releases/tag/0.42.0">beta release</a> 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.</p> <p>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.</p> <p>These release notes cover the major highlights since our beta release. For the full history, see our <a href="https://github.com/facebook/pyrefly/releases">past weekly release notes</a>.</p> <hr /> <h2>Performance Improvements</h2> <p>We've continued to push Pyrefly's performance since the <a href="https://pyrefly.org/blog/2026/02/06/performance-improvements/">speed improvements we shared in February</a>. Since beta:</p> <ul> <li><strong>2–125x faster updated diagnostics</strong> 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</li> <li><strong>20–36% faster full type checking</strong> on large projects like PyTorch and Pandas</li> <li><strong>2–3x faster initial indexing</strong> when Pyrefly first scans your project</li> <li><strong>40–60% less memory usage</strong> during both indexing and incremental type checking</li> </ul> <p>(Tested on an M4 Macbook Pro using open-source benchmarks from <a href="https://github.com/lolpack/type_coverage_py">type_coverage_py</a> and <a href="e990dfd069/scripts/ty_benchmark">ty_benchmark</a>.)</p> <p>Compare the performance of Pyrefly and other Python type checkers on our regularly updated <a href="https://python-type-checking.com/typecheck_benchmark/">benchmarking suite</a>, which runs against 53 popular Python packages.</p> <hr /> <h2>Configuration Presets</h2> <p>A new <code>preset</code> configuration option provides named bundles of error severities and behavior settings.</p> <table> <thead> <tr> <th align="left">Preset</th> <th align="left">Description</th> </tr> </thead> <tbody> <tr> <td align="left"><code>off</code></td> <td align="left">Silences all diagnostics. Useful for IDE-only users or if you want total control of which errors are enabled.</td> </tr> <tr> <td align="left"><code>basic</code></td> <td align="left">Low-noise, high-confidence diagnostics only (syntax errors, missing imports, unknown names, etc.). Ideal for unconfigured projects or IDE-first users.</td> </tr> <tr> <td align="left"><code>legacy</code></td> <td align="left">For codebases migrating from mypy. Disables checks mypy doesn't have. <code>pyrefly init</code> now emits this preset automatically when migrating from a mypy config.</td> </tr> <tr> <td align="left"><code>default</code></td> <td align="left">The standard Pyrefly experience. Equivalent to having no preset.</td> </tr> <tr> <td align="left"><code>strict</code></td> <td align="left">Enables additional strict checks on top of the <code>default</code> preset. For users who want to avoid <code>Any</code> types in their codebase.</td> </tr> </tbody> </table> <p>See the <a href="https://pyrefly.org/en/docs/configuration/#preset">configuration docs</a> for details.</p> <hr /> <h2>Onboarding Experience</h2> <p>We’ve made improvements to the out-of-the-box experience for projects without a <code>pyrefly.toml</code>.</p> <ul> <li><strong>Automatic config synthesis</strong> — 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 <code>pyrefly init</code> would commit to disk.)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="2362c071ca"><code>2362c07</code></a> Bump to version 1.0.0 with release notes</li> <li><a href="471bb8316c"><code>471bb83</code></a> Prep README.md and pyproject.toml for V1</li> <li><a href="f2c6df4c66"><code>f2c6df4</code></a> Use vanity URLs for unconfigured-config upsell</li> <li><a href="d5bf386fd2"><code>d5bf386</code></a> Fix TSP extra IPC connection shutdown hang (<a href="https://redirect.github.com/facebook/pyrefly/issues/3287">#3287</a>)</li> <li><a href="e0a91be416"><code>e0a91be</code></a> do not send snapshotchanged to extra connections</li> <li><a href="3df562c816"><code>3df562c</code></a> extract TypeErrorDisplayStatus into its own module</li> <li>See full diff in <a href="https://github.com/facebook/pyrefly/compare/0.64.1...1.0.0">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 |
Nicolas Vanheuverzwijn |
Sevi C |
Max Ricketts-Uy |
Danny Piper |
|
Byte |
BachErik |
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



