supabase / cli / 29666568199
65%
develop: 65%

LAST BUILD BRANCH: gh-readonly-queue/develop/pr-5919-3fa5a9d9f7106311c8dd06ed9de7cf519856ac88
DEFAULT BRANCH: develop
Ran
Jobs 1
Files 229
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
coverage: 65.08% (+0.02%) from 65.063%
29666568199

push

github

web-flow 
chore(deps): bump the npm-major group with 3 updates (#5903)

Bumps the npm-major group with 3 updates:
[posthog-node](https://github.com/PostHog/posthog-js/tree/HEAD/packages/node),
[fumadocs-core](https://github.com/fuma-nama/fumadocs) and
[fumadocs-ui](https://github.com/fuma-nama/fumadocs).

Updates `posthog-node` from 5.40.0 to 5.41.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/PostHog/posthog-js/releases">posthog-node's
releases</a>.</em></p>
<blockquote>
<h2>posthog-node@5.41.0</h2>
<h2>5.41.0</h2>
<h3>Minor Changes</h3>
<ul>
<li>
<p><a
href="https://redirect.github.com/PostHog/posthog-js/pull/4105">#4105</a>
<a
href="https://github.com/PostHog/posthog-js/commit/203284ad0"><code>203284a</code></a>
Thanks <a
href="https://github.com/eli-r-ph"><code>@​eli-r-ph</code></a>! - Add
opt-in Capture V1 support. Set the <code>POSTHOG_CAPTURE_MODE=v1</code>
environment variable to submit analytics events to the Capture V1
endpoint (<code>/i/v1/analytics/events</code>) instead of the legacy
<code>/batch/</code> endpoint, on both the batched and immediate send
paths. The default remains <code>v0</code>, so existing behavior is
unchanged unless you opt in. Opt-in is env-var-only during the
transition (no public option), so nothing on the API surface has to be
removed when v1 later becomes the default.</p>
<p>Capture V1 uses Bearer auth, lifts legacy <code>$</code>-sentinel
properties into a typed <code>options</code> object, and does per-event
partial retry with exponential backoff clamped against
<code>Retry-After</code>. Dropped and undelivered events are surfaced on
the client <code>error</code> channel as a <code>CaptureV1Error</code>.
<code>$ai_*</code> events continue to use the legacy submitter for now,
regardless of the capture mode.</p>
<p>In <code>v1</code> mode, <code>$ai_*</code> events are routed to an
isolated in-memory queue and flushed independently of the Capture V... (continued)

11145 of 17125 relevant lines covered (65.08%)

10.49 hits per line

Coverage Regressions

Lines Coverage ∆ File
2
82.41
 0.0% internal/storage/rm/rm.go
Jobs
ID Job ID Ran Files Coverage
1 29666568199.1 229
65.08
 GitHub Action Run
Source Files on build 29666568199