• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

supabase / cli / 32913423435
62%
develop: 62%

Build:
Build:
LAST BUILD BRANCH: gh-readonly-queue/develop/pr-6263-40807712e8712fa75141e0dd088ee7054672029d
DEFAULT BRANCH: develop
Ran 26 Aug 2026 12:04AM UTC
Jobs 1
Files 95
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

26 Aug 2026 12:02AM UTC coverage: 62.406%. Remained the same
32913423435

push

github

web-flow
chore(deps-dev): bump verdaccio from 6.9.3 to 6.10.0 in the npm-major group across 1 directory (#6325)

[//]: # (dependabot-start)
⚠️  **Dependabot is rebasing this PR** ⚠️ 

Rebasing might not happen immediately, so don't worry if this takes some
time.

Note: if you make any changes to this PR yourself, they will take
precedence over the rebase.

---

[//]: # (dependabot-end)

Bumps the npm-major group with 1 update in the / directory:
[verdaccio](https://github.com/verdaccio/verdaccio).

Updates `verdaccio` from 6.9.3 to 6.10.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/verdaccio/verdaccio/releases">verdaccio's
releases</a>.</em></p>
<blockquote>
<h2>v6.10.0</h2>
<h3>Minor Changes</h3>
<ul>
<li>
<p>51c2733: Expose the optional legacy authentication cache for
Verdaccio 6.x through <code>server.legacyAuthCache</code>.</p>
<p>This feature is intended for performance-sensitive installations that
still use legacy bearer tokens. When enabled, Verdaccio caches
successful legacy token authentication results for a short period of
time, so repeated requests using the same token do not need to run
password verification through the authentication plugin every time.
Concurrent requests for the same legacy token can also share the same
in-flight authentication result.</p>
<p>The cache is disabled by default, so existing installations keep
their current authentication behavior unless they explicitly opt in.
Basic authentication is not cached. If the cache is enabled, changed or
revoked credentials may remain valid until the cached entry expires.</p>
<p>Enable it in <code>config.yaml</code>:</p>
<pre lang="yaml"><code>server:
  legacyAuthCache:
    enabled: true
    ttlMs: 15000
    maxEntries: 1000
</code></pre>
<p>Options:</p>
<ul>
<li><code>enabled</code>: enables the legacy token authentication cache.
Default: <code>false</code>.</li>
<li><code>ttlMs</code>: time in milliseconds before a cached validation
expires.... (continued)

5571 of 8927 relevant lines covered (62.41%)

6.65 hits per line

Jobs
ID Job ID Ran Files Coverage
1 32913423435.1 26 Aug 2026 12:04AM UTC 95
62.41
GitHub Action Run
Source Files on build 32913423435
  • Tree
  • List 95
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #32913423435
  • a0b4e838 on github
  • Prev Build on develop (#32898033808)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc