dependabot[bot] 39a9d164cf Bump npm-check-updates from 22.2.9 to 23.0.0 in /frontend (#1805)
Bumps
[npm-check-updates](https://github.com/raineorshine/npm-check-updates)
from 22.2.9 to 23.0.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/raineorshine/npm-check-updates/releases">npm-check-updates's
releases</a>.</em></p>
<blockquote>
<h2>v23.0.0</h2>
<h3>⚠️ Breaking changes &amp; migration</h3>
<p><strong>1. Node.js 22+ required</strong> (<a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1844">#1844</a>)
The minimum supported Node.js is now <strong>22</strong>. Supported
versions: <code>^22.22.2 || ^24.15.0 || &gt;=26.0.0</code> (and npm
<code>&gt;=10</code>).</p>
<ul>
<li><em>Migration:</em> Upgrade Node before installing. On older Node,
stay on v22.x.</li>
</ul>
<p><strong>2. Pure ESM package — CJS build dropped, default export is
now callable</strong> (<a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1916">#1916</a>,
<a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1894">#1894</a>)
The package is now pure ESM (no more CommonJS build), and the default
export is now callable directly. <code>ncu.run()</code> and
<code>ncu.defineConfig()</code> still work as namespaced properties.</p>
<ul>
<li><em>Migration (ESM):</em>
<pre lang="js"><code>// before
import * as ncu from 'npm-check-updates'
const upgraded = await ncu.run({ /* ... */ })
// after
import ncu from 'npm-check-updates'
const upgraded = await ncu({ /* ... */ }) // ncu.run({...}) also still
works
</code></pre>
</li>
<li><em>Migration (CommonJS):</em> Still usable via Node's native
<code>require()</code> of ESM (Node 22+), but the import shape changed:
<pre lang="js"><code>// before
const ncu = require('npm-check-updates')
// after
const { default: ncu } = require('npm-check-updates')
ncu({ /* ... */ }).then(upgraded =&gt; console.log(upgraded))
</code></pre>
</li>
</ul>
<p><strong>3. <code>filterVersion</code> / <code>rejectVersion</code> no
longer accept a predicate function. Use <code>filter</code> /
<code>reject</code> instead.</strong> (<a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1933">#1933</a>)
These options now accept only a string, wildcard, glob,
comma/space-delimited list, or <code>/regex/</code>. (CLI usage is
unchanged — the CLI never supported functions.)</p>
<ul>
<li><em>Migration:</em> If you passed a function to
<code>filterVersion</code>/<code>rejectVersion</code> in
<code>.ncurc.js</code> or via the module API, move it to
<code>filter</code> / <code>reject</code> instead. Those receive the
package name <strong>and</strong> the parsed current version, so they
can match on both:
<pre lang="js"><code>// before
filterVersion: (name, semver) =&gt; !(name.startsWith('@myorg/')
&amp;&amp; +semver[0].major &gt; 5)
// after
filter: (name, semver) =&gt; !(name.startsWith('@myorg/') &amp;&amp;
+semver[0].major &gt; 5)
</code></pre>
</li>
</ul>
<p><strong>4. Output is now grouped by default</strong> (<a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1937">#1937</a>)
<code>--format</code> now defaults to <code>[&quot;group&quot;]</code>,
so upgrades are grouped by major / minor / patch out of the box. This is
a better default for most users.</p>
<ul>
<li><em>Migration:</em> To get the old flat output, use:
<pre lang="bash"><code>ncu --format no-group
</code></pre>
The new <code>no-</code> prefix removes a value from the default list
instead of replacing the whole list, so <code>--format
no-group,time</code> disables grouping while adding publish times.</li>
</ul>
<p><strong>5. <code>--target semver</code> now respects explicit upper
bounds</strong> (<a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1920">#1920</a>)
An explicit upper bound in a range is now preserved and never exceeded,
e.g. <code>^9.5.0 &lt;10</code> → <code>^9.7.0 &lt;10</code> (previously
the bound could be overrun). This can change which versions are selected
for ranges with explicit upper bounds.</p>
<h3> Other improvements</h3>
<ul>
<li>Native TypeScript loading (<a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1888">#1888</a>),
lazy-loaded <code>npm-registry-fetch</code> for faster startup (<a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1898">#1898</a>),
and reduced dependencies for a lighter install.</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/raineorshine/npm-check-updates/blob/main/CHANGELOG.md">npm-check-updates's
changelog</a>.</em></p>
<blockquote>
<h2>[23.0.0] - 2026-07-26</h2>
<h3>⚠️ Breaking changes &amp; migration</h3>
<p><strong>1. Node.js 22+ required</strong> (<a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1844">#1844</a>)
The minimum supported Node.js is now <strong>22</strong>. Supported
versions: <code>^22.22.2 || ^24.15.0 || &gt;=26.0.0</code> (and npm
<code>&gt;=10</code>).</p>
<ul>
<li><em>Migration:</em> Upgrade Node before installing. On older Node,
stay on v22.x.</li>
</ul>
<p><strong>2. Pure ESM package — CJS build dropped, default export is
now callable</strong> (<a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1916">#1916</a>,
<a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1894">#1894</a>)
The package is now pure ESM (no more CommonJS build), and the default
export is now callable directly. <code>ncu.run()</code> and
<code>ncu.defineConfig()</code> still work as namespaced properties.</p>
<ul>
<li>
<p><em>Migration (ESM):</em></p>
<pre lang="js"><code>// before
import * as ncu from 'npm-check-updates'
const upgraded = await ncu.run({/* ... */})
// after
import ncu from 'npm-check-updates'
const upgraded = await ncu({/* ... */}) // ncu.run({...}) also still
works
</code></pre>
</li>
<li>
<p><em>Migration (CommonJS):</em> Still usable via Node's native
<code>require()</code> of ESM (Node 22+), but the import shape
changed:</p>
<pre lang="js"><code>// before
const ncu = require('npm-check-updates')
// after
const { default: ncu } = require('npm-check-updates')
ncu({/* ... */}).then(upgraded =&gt; console.log(upgraded))
</code></pre>
</li>
</ul>
<p><strong>3. <code>filterVersion</code> / <code>rejectVersion</code> no
longer accept a predicate function. Use <code>filter</code> /
<code>reject</code> instead.</strong> (<a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1933">#1933</a>)
These options now accept only a string, wildcard, glob,
comma/space-delimited list, or <code>/regex/</code>. (CLI usage is
unchanged — the CLI never supported functions.)</p>
<ul>
<li>
<p><em>Migration:</em> If you passed a function to
<code>filterVersion</code>/<code>rejectVersion</code> in
<code>.ncurc.js</code> or via the module API, move it to
<code>filter</code> / <code>reject</code> instead. Those receive the
package name <strong>and</strong> the parsed current version, so they
can match on both:</p>
<pre lang="js"><code>// before
filterVersion: (name, semver) =&gt; !(name.startsWith('@myorg/')
&amp;&amp; +semver[0].major &gt; 5)
// after
filter: (name, semver) =&gt; !(name.startsWith('@myorg/') &amp;&amp;
+semver[0].major &gt; 5)
</code></pre>
</li>
</ul>
<p><strong>4. Output is now grouped by default</strong> (<a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1937">#1937</a>)
<code>--format</code> now defaults to <code>[&quot;group&quot;]</code>,
so upgrades are grouped by major / minor / patch out of the box. This is
a better default for most users.</p>
<ul>
<li><em>Migration:</em> To get the old flat output, use:</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/raineorshine/npm-check-updates/commit/2417fe3b0ce0356deefa22f1b650afe37e8b5ead"><code>2417fe3</code></a>
23.0.0</li>
<li><a
href="https://github.com/raineorshine/npm-check-updates/commit/61b8818b28dddd2b3810225275d54905677e4ee9"><code>61b8818</code></a>
Update deps (<a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1948">#1948</a>)</li>
<li><a
href="https://github.com/raineorshine/npm-check-updates/commit/548c6e3969865b5c8a5f57ad475617978c343534"><code>548c6e3</code></a>
Merge pull request <a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1943">#1943</a>
from raineorshine/xmr/test-doctor</li>
<li><a
href="https://github.com/raineorshine/npm-check-updates/commit/d31677a3fe9110b0233b5075141ee4464d2c33a3"><code>d31677a</code></a>
test/doctor: run fixtures from a temp copy instead of mutating tracked
files</li>
<li><a
href="https://github.com/raineorshine/npm-check-updates/commit/31c7e85a8ba37a1a1c26154c1f00a2f1aefdec9b"><code>31c7e85</code></a>
Fix and clean up skipped tests (<a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1941">#1941</a>)</li>
<li><a
href="https://github.com/raineorshine/npm-check-updates/commit/c7c968f71aaf67cfc6aefd04ffd16b6c7a97f6a1"><code>c7c968f</code></a>
Merge pull request <a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1935">#1935</a>
from raineorshine/xmr/fix-regex</li>
<li><a
href="https://github.com/raineorshine/npm-check-updates/commit/e42e613794eb89f25c2b32ba6aee9711755edbf6"><code>e42e613</code></a>
Update dependencies (<a
href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1940">#1940</a>)</li>
<li><a
href="https://github.com/raineorshine/npm-check-updates/commit/5c7b4225ff4a299b6bb0c10b3afca6ef5da3d897"><code>5c7b422</code></a>
Add regression test for single-character override keys that are not
'.'</li>
<li><a
href="https://github.com/raineorshine/npm-check-updates/commit/8d0d4be47363891b4362519f64629f12fa8a8609"><code>8d0d4be</code></a>
Move override tests into upgradePackageData.test.ts</li>
<li><a
href="https://github.com/raineorshine/npm-check-updates/commit/21b8f539eb64db2c7156deb8afb51b4e26312ff5"><code>21b8f53</code></a>
Use jsonc-parser for packageManager and JSON catalog upgrades</li>
<li>Additional commits viewable in <a
href="https://github.com/raineorshine/npm-check-updates/compare/v22.2.9...v23.0.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=npm-check-updates&package-manager=npm_and_yarn&previous-version=22.2.9&new-version=23.0.0)](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>
2026-09-01 04:13:30 +00:00

Bracket - Tournament System

build status translations last commit release codecov

Demo · Documentation · Quickstart · GitHub · Releases

evroon/bracket | Trendshift

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.

Explore the Bracket docs  ▶

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

evroon
Erik Vroon
robigan
Null
BachErik
BachErik
ByteAfterlife
Byte
djpiper28
Danny Piper
MaxRickettsUy
Max Ricketts-Uy
sevi418
Sevi C
nvanheuverzwijn
Nicolas Vanheuverzwijn
aminnairi
Amin NAIRI
FelipeGdM
Felipe Gomes De Melo
IzStriker
IzStriker
jmillxyz
Jon Miller
babeuh
Raphael Le Goaller

License

Bracket is licensed under AGPL-v3.0.

Please note that any contributions also fall under this license.

See LICENSE

S
Description
No description provided
Readme AGPL-3.0
55 MiB
0 Stars 1 Watchers 0 Forks
Languages
TypeScript 51%
Python 47.7%
CSS 0.8%
Dockerfile 0.2%