5bd2a5bd24
Bumps [pyrefly](https://github.com/facebook/pyrefly) from 1.0.0 to 1.1.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 v1.1.1</h2> <p><em>Release date: June 18, 2026</em></p> <p>Pyrefly v1.1.1 is a patch release with a single bug fix.</p> <hr /> <h2>🐛 Bug fixes</h2> <ul> <li><strong><a href="https://redirect.github.com/facebook/pyrefly/issues/3867">#3867</a>:</strong> Fixed a regression introduced in 1.1.0 where <code>isinstance()</code> narrowing of a union variable silently stopped working when an earlier sibling branch in the same <code>if</code>/<code>elif</code>/<code>else</code> chain narrowed a different variable with <code>isinstance()</code> and returned. The later narrowing left the union untouched, producing false <code>missing-attribute</code> errors on code that checked correctly in 1.0.0.</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="bash"><code>pip install --upgrade pyrefly==1.1.1 </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> <ol> <li><code>pyrefly check --suppress-errors</code></li> <li>Run your code formatter of choice</li> <li><code>pyrefly check --remove-unused-ignores</code></li> <li>Repeat until you achieve a clean formatting run and a clean type check.</li> </ol> <p>This will add <code># pyrefly: ignore</code> 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.</p> <p>Read more about error suppressions in the <a href="https://pyrefly.org/en/docs/error-suppressions/">Pyrefly documentation</a>.</p> <h2>Pyrefly v1.1.0</h2> <p><em>Release date: June 17, 2026</em></p> <p>Pyrefly v1.1.0 bundles <strong>250 commits</strong> from <strong>25 contributors</strong>.</p> <hr /> <h2>✨ New & Improved</h2> <h3>Type Checking</h3> <ul> <li>Pyrefly now correctly narrows <code>TypedDict</code> types after <code>isinstance(x, dict)</code> checks, treating them as runtime <code>dict</code> instances while preserving field information in the positive branch.</li> <li>Type narrowing for bounded and constrained <code>TypeVar</code>s has been significantly improved. <code>isinstance</code> checks now correctly narrow <code>Self</code> and bounded type variables via their disjoint-base representatives, and negative narrowing on bounded TypeVars no longer produces false positives.</li> <li>Constrained <code>TypeVar</code>s are now preserved through method calls and binary operations, so <code>T & int</code> where <code>T: (int, str)</code> correctly returns <code>T & int</code> instead of losing the TypeVar.</li> <li>Classes decorated with <code>@dataclass(slots=True)</code> are now recognized as PEP 800 disjoint bases when they synthesize non-empty <code>__slots__</code>, enabling proper multiple-inheritance conflict detection and type narrowing.</li> <li>Pyrefly now detects when methods override parent class methods without using the <code>@override</code> decorator, and a new quick fix can automatically add the decorator for you.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="b87de05834"><code>b87de05</code></a> cut 1.1.1</li> <li><a href="a297847fa0"><code>a297847</code></a> release notes for v1.1.1</li> <li><a href="4be8673788"><code>4be8673</code></a> Fix isinstance narrowing silently breaking after a sibling branch narrows ano...</li> <li><a href="67a11d42e5"><code>67a11d4</code></a> cut 1.1.0</li> <li><a href="6eb38a7c37"><code>6eb38a7</code></a> Handle empty name invalid syntax</li> <li><a href="54f61bc104"><code>54f61bc</code></a> Resolve type-alias refs against their own module, not typing</li> <li><a href="fc495dc8a7"><code>fc495dc</code></a> add test for resolving type alias references</li> <li><a href="33de466bda"><code>33de466</code></a> Resolve real source locations by reusing the query transaction (<a href="https://redirect.github.com/facebook/pyrefly/issues/3829">#3829</a>)</li> <li><a href="3fd550de5b"><code>3fd550d</code></a> Teach the type converter to resolve export locations</li> <li><a href="86f0da71bd"><code>86f0da7</code></a> Lazy materialize implicit builtins</li> <li>Additional commits viewable in <a href="https://github.com/facebook/pyrefly/compare/1.0.0...1.1.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 |
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