|
Ran
|
Jobs
36
|
Files
166
|
Run time
1min
|
Badge
README BADGES
|
push
github
chore(deps): bump supabase/setup-cli from 3.0.1 to 3.1.0 (#1909) Bumps [supabase/setup-cli](https://github.com/supabase/setup-cli) from 3.0.1 to 3.1.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/supabase/setup-cli/releases">supabase/setup-cli's releases</a>.</em></p> <blockquote> <h2>v3.1.0</h2> <h2>Summary</h2> <ul> <li><code>version</code> accepts the <code>next</code> and <code>v<N>.stable</code> dist-tags, so a workflow can stay on an older major's maintenance line, for example <code>version: v2.stable</code> (<a href="https://redirect.github.com/supabase/setup-cli/pull/456">#456</a>).</li> <li>When npm can't install a working CLI yet, for example while a new release is still propagating, the action installs the same version from its GitHub release instead. <ul> <li>It verifies the download against the release's checksums.</li> <li>It needs a fixed version, either requested or resolved by npm.</li> <li>It is skipped when the lockfile integrity check fails.</li> <li>The new <code>install-source</code> output reports <code>npm</code> or <code>github-release</code>. (<a href="https://redirect.github.com/supabase/setup-cli/pull/457">#457</a>)</li> </ul> </li> <li>The README documents the <code>v3</code> tag publish flow (<a href="https://redirect.github.com/supabase/setup-cli/pull/455">#455</a>).</li> </ul> <h2>Validation</h2> <ul> <li>CI and E2E passed on <code>main</code> before tagging.</li> </ul> <p><code>v3</code> is the moving major-version alias for this release.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/supabase/setup-cli/commit/d239d1052"><code>d239d10</code></a> feat: fall back to the GitHub release when npm cannot install the CLI (<a href="https://redirect.github.com/supabase/setup-cli/issues/457">#457</a>)</li> <li><a href="https://github.com/supabase/setup-cli/commit/bea637206310b05056109c4ffab... (continued)
12151 of 12751 relevant lines covered (95.29%)
5.91 hits per line
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|