mirror of
https://github.com/evroon/bracket.git
synced 2026-06-11 18:24:38 -04:00
fe67b0c120
Bumps [pyrefly](https://github.com/facebook/pyrefly) from 0.48.0 to 0.50.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 v0.49.0</h2> <p><strong>Status : BETA</strong><br /> <em>Release date: 20 January 2026</em></p> <p>Pyrefly v0.49.0 bundles <strong>231 commits</strong> from <strong>25 contributors</strong>.</p> <hr /> <h1>✨ New & Improved</h1> <table> <thead> <tr> <th align="left">Area</th> <th align="left">What’s new</th> </tr> </thead> <tbody> <tr> <td align="left"><strong>Type Inference</strong></td> <td align="left">- Partial type inference now possible in loops <!-- raw HTML omitted --><!-- raw HTML omitted -->- Variance inference for self-referential generic types (PEP 695) <!-- raw HTML omitted --><!-- raw HTML omitted -->- <code>typing.Mapping</code> now recognised as a type alias</td> </tr> <tr> <td align="left"><strong>Language Server</strong></td> <td align="left">- Improved refactoring capabilities for moving module members and lifting local functions/methods to top-level module scope, with automatic import/shim creation. <!-- raw HTML omitted --><!-- raw HTML omitted -->- Hover support for <code>in</code> keyword when used in iteration contexts (for-loops and comprehensions), showing the type of the iterable being iterated over <!-- raw HTML omitted --><!-- raw HTML omitted -->- “Go to symbol” now correctly includes methods inside a class <!-- raw HTML omitted --><!-- raw HTML omitted -->- Enabled clickable inlay hints for built-in types like tuple, dict, str, and special forms (TypeVar, ParamSpec, etc.), allowing users to quickly navigate to type definitions in the IDE</td> </tr> <tr> <td align="left"><strong>Pydantic Support</strong></td> <td align="left">Added detection and support for <code>pydantic.dataclasses.dataclass</code> decorator, including strict and lax mode support for pydantic dataclasses</td> </tr> <tr> <td align="left"><strong>Error Reporting</strong></td> <td align="left">Improved error messages for <code>yield</code>, <code>yield from</code>, augmented assignment, missing imports, and missing stubs for better user clarity.</td> </tr> </tbody> </table> <hr /> <h1>🐛 bug fixes</h1> <p>We closed <strong>38 bug issues</strong> this week 👏</p> <ul> <li><a href="https://redirect.github.com/facebook/pyrefly/issues/2145">#2145</a> - Fixed variance inference incorrectly using <code>inferred_variance</code> instead of <code>specified_variance</code> for stdlib generic classes like <code>Mapping[str, T]</code>.</li> <li><a href="https://redirect.github.com/facebook/pyrefly/issues/1806">#1806</a> - Fixed improper type narrowing and captured variable typing for sequence patterns (e.g., <code>[*values]</code>) in match/case statements.</li> <li><a href="https://redirect.github.com/facebook/pyrefly/issues/1697">#1697</a> - Fixed a bug where Pyrefly got confused if a class had the same name as an overloaded method.</li> <li><a href="https://redirect.github.com/facebook/pyrefly/issues/1494">#1494</a> - Ensures correct overload resolution when promoting nested tuple element literals for unannotated method-initialized attributes.</li> <li>And more: <a href="https://redirect.github.com/facebook/pyrefly/issues/1481">#1481</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1472">#1472</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1466">#1466</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1385">#1385</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1341">#1341</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1310">#1310</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1277">#1277</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1234">#1234</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1219">#1219</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1208">#1208</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1013">#1013</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1002">#1002</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/935">#935</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/910">#910</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/899">#899</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/773">#773</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/768">#768</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/755">#755</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/737">#737</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/708">#708</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/421">#421</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/295">#295</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/266">#266</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/265">#265</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1503">#1503</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1616">#1616</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1626">#1626</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/1803">#1803</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/2051">#2051</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/2072">#2072</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/2077">#2077</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/2107">#2107</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/2111">#2111</a>, <a href="https://redirect.github.com/facebook/pyrefly/issues/2161">#2161</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 /> <h1>📦 Upgrade</h1> <pre><code>pip install --upgrade pyrefly==0.49.0 </code></pre> <h2>How to safely upgrade your codebase</h2> <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> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="4c95fadbff"><code>4c95fad</code></a> Allow suppress command to take in json values (4/n)</li> <li><a href="ddc207782f"><code>ddc2077</code></a> Disable test failing on Windows</li> <li><a href="5d09330250"><code>5d09330</code></a> Fix completion item kinds for module attributes (<a href="https://redirect.github.com/facebook/pyrefly/issues/1936">#1936</a>)</li> <li><a href="c57c5e5659"><code>c57c5e5</code></a> Fix go-to-definition for intermediate submodule components</li> <li><a href="c5b01d308b"><code>c5b01d3</code></a> Add go-to-def test for deep submodule chain with explicit re-exports</li> <li><a href="46a55b2462"><code>46a55b2</code></a> make --remove-unused-ignores a no-op for files with no unused ignores (<a href="https://redirect.github.com/facebook/pyrefly/issues/2217">#2217</a>)</li> <li><a href="bdac377cc3"><code>bdac377</code></a> fix relative pyrefly.org link in documentation (<a href="https://redirect.github.com/facebook/pyrefly/issues/2186">#2186</a>)</li> <li><a href="ab05550d2d"><code>ab05550</code></a> Update pyrefly version]</li> <li><a href="06583faa51"><code>06583fa</code></a> Simplify tarjan NodeVec push</li> <li><a href="063154c9fa"><code>063154c</code></a> Refactor IsInstancePattern to use NarrowSource on IsInstance</li> <li>Additional commits viewable in <a href="https://github.com/facebook/pyrefly/compare/0.48.0...0.50.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 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) </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