Update dependency posthog-node to v5.53.0 by renovate[bot] · Pull Request #318 · Hack-PSU/adminv2

renovate · 2026-03-26T17:46:23Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
posthog-node (source)	`5.28.5` → `5.53.0`

Release Notes

PostHog/posthog-js (posthog-node)

`v5.53.0`

Compare Source

Minor Changes

#5050 31dd1ad Thanks @posthog! - Read a feature flag's evaluation runtime with getFeatureFlagEvaluationRuntime(key) and getFeatureFlagKeysByEvaluationRuntime(runtime)
(2026-09-23)

`v5.52.6`

Compare Source

Patch Changes

#5078 f4704ac Thanks @rubychilds! - Honor filters.holdout during local feature flag evaluation. A user in an experiment holdout now receives the holdout-<id> variant instead of being bucketed into a regular variant, matching how the server evaluates the same flag. The holdout is resolved before the release conditions, so a held-out user never reaches the flag's targeting — including when those conditions would have excluded them, so isFeatureEnabled can return true where it previously returned false. Experiments with an active holdout will see variant assignment change for the held-out share of traffic on upgrade, bringing locally evaluated assignments in line with server-evaluated ones.
(2026-09-23)
Updated dependencies [f4704ac]:
- @posthog/core@1.55.2

`v5.52.5`

Compare Source

Patch Changes

#5018 9cd8ebd Thanks @turnipdabeets! - Stop dropping long spans that end: maxSpanAgeMs now evicts spans only once maxLiveSpans is reached, so a span that runs past the age limit and then ends is exported, and its children are no longer orphaned.
(2026-09-21)
#4800 aad7464 Thanks @marandaneto! - Respect the definitions response's property_matching_version during local feature flag evaluation. Version 2 uses explicit boolean/string equality and per-member array matching, while missing or other versions retain service legacy matching (including empty-array truthiness). Preserve the version in Node definition caches and Convex persisted definitions, and propagate it through person, group, cohort and dependency evaluation without mixing snapshots during reloads. Existing numeric ambiguity fallback and SemVer parsing policies are unchanged.
(2026-09-21)
Updated dependencies [9cd8ebd, aad7464]:
- @posthog/core@1.55.1

`v5.52.4`

Compare Source

Patch Changes

#4885 39a8980 Thanks @decknamec! - Server-side feature flags now resolve in posthog-node and posthog-edge even when a proxy rewrites the request's User-Agent. Flags restricted to the client runtime now resolve to undefined in these SDKs, where a rewritten User-Agent previously let them through.
(2026-09-15)
Updated dependencies [39a8980]:
- @posthog/core@1.54.2

`v5.52.3`

Compare Source

Patch Changes

#4941 07c1045 Thanks @marandaneto! - Capture causes and AggregateError members with relationship metadata and individual stacks, limiting output to 50 entries and 1,000 member inspections.
(2026-09-15)
Updated dependencies [07c1045]:
- @posthog/core@1.54.1

`v5.52.2`

Compare Source

Patch Changes

#4951 55c5142 Thanks @marandaneto! - Fix Express exception events reporting the initial response status instead of the final HTTP status.
(2026-09-14)

`v5.52.1`

Compare Source

Patch Changes

#4908 4a3c74b Thanks @turnipdabeets! - Child spans now share their parent's clock, so a child no longer appears to start before or end after its parent by up to a millisecond, or by more when the system clock is adjusted mid-trace.
(2026-09-11)
Updated dependencies [4a3c74b]:
- @posthog/core@1.53.1

`v5.52.0`

Compare Source

Minor Changes

#4579 19e78cc Thanks @turnipdabeets! - Add experimental distributed tracing to posthog-node: startSpan, withSpan and getActiveSpan record spans against a new traces client option. A service with tracing off still forwards an inbound traceparent, including from spans nested inside the one that received it, so a distributed trace is not severed. A traceparent may be passed as the one-element array req.headersDistinct gives. A beforeSpanSend hook sees every span before it is exported and may edit or drop it, and maxAttributesPerSpan, maxEventsPerSpan, maxAttributeValueLength, maxLiveSpans and maxSpanAgeMs bound what a single span and a single process may hold.
(2026-09-10)

Patch Changes

#4579 19e78cc Thanks @turnipdabeets! - Stop a throwing getter in metrics.resourceAttributes from breaking every metrics export — the key is recorded as [Unserializable] instead.
(2026-09-10)
#4579 19e78cc Thanks @turnipdabeets! - Honor Retry-After when the ingestion endpoint refuses a logs or metrics batch, instead of retrying on the SDK's own schedule alone. A refusal naming a longer wait extends the one being served, up to five minutes from when it started. Retry delays now carry jitter so clients refused together do not return together, and metrics backs off exponentially across consecutive failures rather than retrying on a fixed interval.
(2026-09-10)
#4579 19e78cc Thanks @turnipdabeets! - Logs and metrics now always send service.name and telemetry.sdk.*, even when a resourceAttributes value is too large to encode in full. Previously that value could crowd them out, and the records reached PostHog with no service attribution.
(2026-09-10)
#4579 19e78cc Thanks @turnipdabeets! - Stop sending logs and metrics batches over 10 MiB, or too large to serialize at all, instead of spending a request to discover the endpoint refuses them.
(2026-09-10)
Updated dependencies [19e78cc, 19e78cc, 19e78cc, 19e78cc, 19e78cc, 19e78cc, 19e78cc]:
- @posthog/core@1.53.0

`v5.51.8`

Compare Source

Patch Changes

#4798 4358915 Thanks @posthog! - fix(error-tracking): collapse repeated frame cycles in parsed stack traces to reduce grouping differences caused by recursion depth, while preserving distinct throw locations
(2026-09-09)
Updated dependencies [4358915]:
- @posthog/core@1.51.1

`v5.51.7`

Compare Source

Patch Changes

#4785 74ca945 Thanks @marandaneto! - Clarify feature flag return-value terminology across SDK APIs. A false value is a conclusive off evaluation, while undefined means no evaluation is available. Remote evaluation omits globally inactive flags, whereas backend local evaluation can resolve cached inactive definitions to false.
(2026-09-07)
Updated dependencies [74ca945]:
- @posthog/core@1.50.6

`v5.51.6`

Compare Source

Patch Changes

#4719 56148bd Thanks @github-actions! - Expose exception capture methods through the IPostHog interface.
(2026-09-01)

`v5.51.5`

Compare Source

Patch Changes

#4661 444bf35 Thanks @marandaneto! - Match local feature flag string operators, exact-value coercion, and JSON stringification with the flags service.
(2026-09-01)
#4708 6723395 Thanks @turnipdabeets! - Change bigint attributes on logs, metrics and spans to send as an int64 rather than as a string.
(2026-09-01)
Updated dependencies [444bf35, 6ae173f, 6723395]:
- @posthog/core@1.50.0

`v5.51.4`

Compare Source

Patch Changes

#4636 74ff567 Thanks @yfwmaniish! - Narrow the pinterest entry in the bot-detection blocklist to pinterestbot, so real users on Pinterest's in-app browser (whose UA also contains the substring pinterest) are no longer misclassified as bots and silently excluded from analytics. The crawler's other UA variant remains covered by the existing generic bot.htm entry, so no bot-detection coverage is lost.
(2026-08-27)
#4660 dfc3b59 Thanks @posthog! - Honor evaluationContexts during local evaluation — flags whose evaluation contexts don't overlap the configured list are no longer evaluated locally and resolve to undefined.
(2026-08-27)
Updated dependencies [74ff567]:
- @posthog/core@1.49.1

`v5.51.3`

Compare Source

Patch Changes

#4651 e899b1c Thanks @marandaneto! - Treat omitted local evaluation properties as inconclusive for is_not_set.
(2026-08-27)
Updated dependencies [7902e44, e899b1c]:
- @posthog/core@1.48.12

`v5.51.2`

Compare Source

Patch Changes

#4639 1faeb74 Thanks @marandaneto! - Handle empty feature flag evaluation key scopes without running local or remote evaluation.
(2026-08-25)
#4610 930de19 Thanks @marandaneto! - Share feature flag matching, hashing, variant, and payload evaluation helpers across the Node.js and Convex SDKs without changing their runtime-specific SemVer behavior.
(2026-08-25)
Updated dependencies [930de19, d4eee8f]:
- @posthog/core@1.48.11

`v5.51.1`

Compare Source

Patch Changes

#4614 3593c43 Thanks @iamomiid! - The Node SDK now sends the raw gzip bytes as the request body instead of wrapping them in a Blob. On Node 24.16 and later, reading a Blob request body leaks a native BlobReader that is never released, so a service calling capture() and flush() once per request grew by roughly 2.3 KB of heap per event and never gave it back. This completes the work in #4423: switching to node:zlib removed the compression-time Blob reads, but the body itself was still a Blob and still got read once per request. Compression behaviour, headers and the wire format are unchanged, and the edge build keeps using CompressionStream.
(2026-08-24)
Updated dependencies [3593c43]:
- @posthog/core@1.48.9

`v5.51.0`

Compare Source

Minor Changes

#4564 233ac88 Thanks @marandaneto! - Fall back to remote evaluation when a requested flag is missing from loaded local definitions. This
changes scoped calls that previously omitted the flag without making a request. (2026-08-24)

`v5.50.0`

Compare Source

Minor Changes

#4484 557140e Thanks @posthog! - FeatureFlagEvaluations.isEnabled() now accepts an optional defaultValue option, returned whenever the flag has no value (missing key, not loaded, or a failed request). A flag with a present value — including false and variant strings — always wins over defaultValue. Purely additive; omitting the option preserves the existing false-on-miss behavior.
(2026-08-21)

`v5.49.4`

Compare Source

Patch Changes

#4569 00d22ea Thanks @v11t! - fix getFeatureFlagResult returning null variant instead of undefined when remotely evaluated
(2026-08-21)

`v5.49.3`

Compare Source

Patch Changes

#4583 6322f09 Thanks @turnipdabeets! - Fix logs and metrics being silently dropped when an attribute holds a very large integer, a function, a symbol, a sparse array, or a truncated emoji.
Cap log and metric attributes at 20 levels of nesting, 1,000 entries per object and 10,000 values in total, marking anything beyond as [Truncated].
Type OtlpAnyValue.intValue as string | number — code reading that field must handle both. (2026-08-21)
Updated dependencies [6322f09]:
- @posthog/core@1.48.7

`v5.49.2`

Compare Source

Patch Changes

#4578 bae46bf Thanks @marandaneto! - Drop events when a before-send hook throws instead of sending the unmodified event.
(2026-08-20)
Updated dependencies [bae46bf, aef2f49]:
- @posthog/core@1.48.6

`v5.49.1`

Compare Source

Patch Changes

#4521 0a0206f Thanks @marandaneto! - Normalize capture timestamp overrides to equivalent UTC ISO strings in the browser and Node.js SDKs and shared core.
(2026-08-14)
Updated dependencies [0a0206f]:
- @posthog/core@1.48.1

`v5.49.0`

Compare Source

Minor Changes

#4289 c9086de Thanks @carlos-marchal-ph! - Public beta captureAi() / captureAiImmediate(): AI events on a dedicated isolated endpoint with the event UUID returned. New enableFullAiCapture option replaces the internal _useAiLane / _enableMultimodalCapture; wrappers route through the AI endpoint and skip redaction/truncation when set (privacy mode still wins).
(2026-08-13)

Patch Changes

Updated dependencies [c9086de]:
- @posthog/core@1.48.0

`v5.48.2`

Compare Source

Patch Changes

#4506 a77115b Thanks @marandaneto! - Log shutdown timeouts without rejecting, and correct the Node.js shutdown() return type to Promise<void>.
(2026-08-12)
Updated dependencies [a77115b]:
- @posthog/core@1.47.1

`v5.48.1`

Compare Source

Patch Changes

#4346 4751b33 Thanks @marandaneto! - Enforce configured request timeouts while consuming Capture V1 response bodies.
(2026-08-06)
#4423 64ba193 Thanks @marandaneto! - Use Node's zlib gzip implementation for Node SDK payloads to avoid sustained memory growth from frequent Web Streams compression.
(2026-08-06)
Updated dependencies [64ba193]:
- @posthog/core@1.46.9

`v5.48.0`

Compare Source

Minor Changes

#4342 fa3457f Thanks @haacked! - Support the starts_with, not_starts_with, ends_with, and not_ends_with property filter operators in feature flag local evaluation. Matching is case-insensitive and mirrors icontains, so flags using these operators no longer fall back to remote evaluation.
(2026-08-05)

`v5.47.11`

Compare Source

Patch Changes

#4380 3c40b6c Thanks @marandaneto! - Keep request timeouts active through response body consumption and clarify eventual event UUID deduplication semantics.
(2026-08-05)
Updated dependencies [3c40b6c]:
- @posthog/core@1.46.8

`v5.47.10`

Compare Source

Patch Changes

#4287 d3c4538 Thanks @posthog! - Keep $referring_domain and canonical utm_*/campaign parameters on minimal $feature_flag_called events. Previously the minimal allowlist stripped every campaign parameter, so a flag-called event landing first in a session could set the session's UTM attribution and channel type to NULL in web analytics.
(2026-08-04)
Updated dependencies [d3c4538]:
- @posthog/core@1.46.7

`v5.47.9`

Compare Source

Patch Changes

#4350 facb4c1 Thanks @marandaneto! - Fix enableExceptionAutocapture suppressing Node's default crash on unhandled promise rejections; fatal rejections in strict or warn-with-error-code mode and rejections handled by another unhandledRejection listener are no longer captured.
(2026-08-04)

`v5.47.8`

Compare Source

Patch Changes

#4348 d4ffb83 Thanks @marandaneto! - Schedule local feature flag polls after each request settles.
(2026-08-04)
Updated dependencies [821a2c6]:
- @posthog/core@1.46.6

`v5.47.7`

Compare Source

Patch Changes

#4352 1cf9c6d Thanks @marandaneto! - Bound stack source context reads and skip non-regular or oversized files.
(2026-08-03)

`v5.47.6`

Compare Source

Patch Changes

#4381 f3a71a1 Thanks @marandaneto! - Clear completed lifecycle timeout handles so successful shutdowns do not leave timers running.
(2026-08-03)
Updated dependencies [f3a71a1]:
- @posthog/core@1.46.4

`v5.47.5`

Compare Source

Patch Changes

#4155 eb0a793 Thanks @ATKasem! - fix: personProperties and groupProperties on the feature flag methods are no longer typed as Record<string, string>, so numeric and boolean values type-check without a cast. Local evaluation already handled them — matchProperty takes Record<string, any> and compares numerically for gt/gte/lt/lte — only the public types disagreed. These now use the shared Properties type (personProperties?: Properties, groupProperties?: Record<string, Properties>), matching setPersonPropertiesForFlags/setGroupPropertiesForFlags so the any can be narrowed later. Types only, no runtime change.
(2026-08-03)
Updated dependencies [eb0a793]:
- @posthog/core@1.46.3

`v5.47.4`

Compare Source

Patch Changes

#4347 7c3a9af Thanks @marandaneto! - Preserve events added to a full queue while an earlier batch is being flushed.
(2026-08-03)
Updated dependencies [7c3a9af]:
- @posthog/core@1.46.2

`v5.47.3`

Compare Source

Patch Changes

#4349 0e2b371 Thanks @marandaneto! - Apply the feature flag definition request timeout while consuming the response body.
(2026-07-31)
#4349 0e2b371 Thanks @marandaneto! - Keep the feature flag definition request timeout active until the request settles.
(2026-07-31)

`v5.47.2`

Compare Source

Patch Changes

#4332 b9a241e Thanks @ioannisj! - Fix identify() leaving a user anonymous when the supplied ID already matches the persisted distinct ID (for example after a non-identified bootstrap seeded the same ID). The user is now marked identified and a person-processed $set event is captured. Ports the same fix from posthog-js (browser) to the shared core used by React Native, Node, and posthog-js-lite.
(2026-07-31)
Updated dependencies [b9a241e]:
- @posthog/core@1.46.1

`v5.47.1`

Compare Source

Patch Changes

#4380 3c40b6c Thanks @marandaneto! - Keep request timeouts active through response body consumption and clarify eventual event UUID deduplication semantics.
(2026-08-05)
Updated dependencies [3c40b6c]:
- @posthog/core@1.46.8

`v5.47.0`

Compare Source

Minor Changes

#4308 6e7f3ae Thanks @ablaszkiewicz! - Emit the release id that posthog-cli injects into your bundle as $release_id on $exception events, so PostHog can attach exceptions to a release without joining through symbol sets. Adds getInjectedReleaseId() to @posthog/core. The property is only attached when an injected release id can be read.
(2026-07-30)

Patch Changes

Updated dependencies [6e7f3ae]:
- @posthog/core@1.46.0

`v5.46.1`

Compare Source

Patch Changes

#4234 6c8fde0 Thanks @hpouillot! - Normalize V8 Promise combinator stack frames so input indexes are not treated as source filenames.
(2026-07-23)
Updated dependencies [6c8fde0]:
- @posthog/core@1.45.1

`v5.46.0`

Compare Source

Minor Changes

#4172 9621830 Thanks @haacked! - send minimal $feature_flag_called events when the server enables it

When the v2 /flags response carries minimalFlagCalledEvents: true (or, for posthog-node local evaluation, the flag-definitions payload carries minimal_flag_called_events: true) and the evaluated flag is not linked to an experiment ($feature_flag_has_experiment === false), $feature_flag_called events are rebuilt from a strict allowlist of flag-evaluation, processing-control, and SDK-identity properties. Super properties, $set/$set_once, the $feature/<key> enumeration, $active_feature_flags, and the context envelope are stripped. Any missing signal (no gate on the response, bootstrapped or locally injected flags, has_experiment unknown) falls back to the full event, and experiment-linked flags always send the full envelope. The gate is stored alongside the cached flags (posthog-js persistence, posthog-node poller state) and is server-controlled, with no SDK-side configuration. before_send runs after the filter and may re-add stripped properties. (2026-07-20)

Patch Changes

Updated dependencies [9621830]:
- @posthog/core@1.44.0

`v5.45.2`

Compare Source

Patch Changes

#4168 06d19a2 Thanks @dustinbyrne! - Avoid Next.js Edge runtime warnings for native compression and fatal error handling.
(2026-07-16)
Updated dependencies [06d19a2]:
- @posthog/core@1.43.1

`v5.45.1`

Compare Source

Patch Changes

#4164 9eb2b28 Thanks @dustinbyrne! - Fix the default Node.js event flush interval at 5 seconds.
(2026-07-16)

`v5.45.0`

Compare Source

Minor Changes

#4159 fad6d9a Thanks @haacked! - add $feature_flag_has_experiment to $feature_flag_called events

$feature_flag_called events now carry a $feature_flag_has_experiment boolean sourced from the server's has_experiment flag metadata (the /flags?v=2 response for remote evaluation, the /api/feature_flag/local_evaluation definitions for posthog-node local evaluation). The property is only sent when the server explicitly reports has_experiment; it is omitted entirely when the value is unknown (older servers, missing metadata, bootstrapped or locally injected flags). (2026-07-16)

Patch Changes

Updated dependencies [fad6d9a]:
- @posthog/core@1.43.0

`v5.44.0`

Compare Source

Minor Changes

#4153 fc2cb2e Thanks @eli-r-ph! - Raise the default maxQueueSize from 1000 to 10000. Backend workloads are more likely to burst-enqueue events synchronously ahead of a flush than browser/mobile clients, so the previous default risked silently dropping events under bursty load. An explicit maxQueueSize option still overrides this default.
(2026-07-15)

Patch Changes

Updated dependencies [fc2cb2e]:
- @posthog/core@1.42.1

`v5.43.0`

Compare Source

Minor Changes

#4117 1eddff7 Thanks @DanielVisca! - add the posthog.metrics API (count, gauge, histogram) to posthog-node — alpha

Backend services can now record metrics through the same statsd-style pre-aggregating client the browser SDK ships, with no OpenTelemetry setup:
```
const client = new PostHog('phc_...', { metrics: { serviceName: 'billing-worker' } })
client.metrics.count('invoices.processed', 1, { attributes: { plan: 'pro' } })
client.metrics.gauge('queue.depth', 42)
client.metrics.histogram('job.duration', 187, { unit: 'ms' })
```
Samples aggregate in memory and flush as OTLP/JSON to /i/v1/metrics (one data point per series per window). Pending metrics are flushed on shutdown(). Core gains _sendMetricsBatch on PostHogCoreStateless (same outcome contract as _sendLogsBatch) and a shared resolveMetricsConfig, so any core-based SDK can host PostHogMetrics. (2026-07-15)

Patch Changes

Updated dependencies [1eddff7]:
- @posthog/core@1.42.0

`v5.42.0`

Compare Source

Minor Changes

#4101 dc2aa5b Thanks @posthog! - Expose the error tracking rate-limiter config via the new exceptionRateLimiterRefillRate and exceptionRateLimiterBucketSize options. Burst protection is scoped per exception type (each distinct $exception type gets its own token bucket, with no aggregate cap across types), so these let customers with high-cardinality exception types tune the per-type allowance.
(2026-07-14)

Patch Changes

Updated dependencies [dc2aa5b]:
- @posthog/core@1.41.0

`v5.41.0`

Compare Source

Minor Changes

#4105 203284a Thanks @eli-r-ph! - Add opt-in Capture V1 support. Set the POSTHOG_CAPTURE_MODE=v1 environment variable to submit analytics events to the Capture V1 endpoint (/i/v1/analytics/events) instead of the legacy /batch/ endpoint, on both the batched and immediate send paths. The default remains v0, 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.

Capture V1 uses Bearer auth, lifts legacy $-sentinel properties into a typed options object, and does per-event partial retry with exponential backoff clamped against Retry-After. Dropped and undelivered events are surfaced on the client error channel as a CaptureV1Error. $ai_* events continue to use the legacy submitter for now, regardless of the capture mode.

In v1 mode, $ai_* events are routed to an isolated in-memory queue and flushed independently of the Capture V1 queue, so the two transports never share a batch and a failure on one cannot re-send events already accepted on the other. Each queue keeps its own retry/durability semantics: the legacy queue re-queues on network failure (retrying on later flushes), while the V1 queue exhausts the sender's own attempt budget per cycle and then surfaces the failure rather than re-queuing. (2026-07-11)

Patch Changes

Updated dependencies [203284a]:
- @posthog/core@1.40.2

`v5.40.0`

Compare Source

Minor Changes

#4060 0b49a4c Thanks @turnipdabeets! - Add secretKey config as the canonical alias for the deprecated personalApiKey (accepts a Personal API Key or Project Secret API Key).
(2026-07-07)

`v5.39.4`

Compare Source

Patch Changes

#4047 0c11747 Thanks @marandaneto! - Stop duplicating distinct_id inside /flags person properties.
(2026-07-02)
Updated dependencies [5e7e132]:
- @posthog/core@1.39.5

`v5.39.3`

Compare Source

Patch Changes

#4055 64e04ba Thanks @marandaneto! - Retry /flags requests that receive HTTP 502 or 504 responses across SDKs that use the shared core flags client.
(2026-07-02)
Updated dependencies [64e04ba]:
- @posthog/core@1.39.4

`v5.39.2`

Compare Source

Patch Changes

#4028 a664b81 Thanks @marandaneto! - Make Node flush() wait for pending asynchronous SDK work before draining the event queue, so events produced by helpers like captureException() are not missed. Pending work rejections no longer prevent queued events from flushing.
(2026-07-01)
Updated dependencies [a664b81]:
- @posthog/core@1.39.3

`v5.39.1`

Compare Source

Patch Changes

#4029 b36b1cc Thanks @marandaneto! - Call before_send for identify, group identify, and alias events.
(2026-06-30)
#4027 ab118d2 Thanks @marandaneto! - Safely serialize event batches with circular property references instead of crashing during flush.
(2026-06-30)
Updated dependencies [ab118d2]:
- @posthog/core@1.39.2

`v5.39.0`

[Compare Source](https://redirect.github.com/PostHog/posthog-js/co

❗ Important

✂ PR body was truncated to here.

Configuration

📅 Schedule: (in timezone America/New_York)

Branch creation
- Between 12:00 AM and 11:59 PM (* 0-23 * * *)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

vercel · 2026-03-26T17:46:28Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
adminv2	Ready	Preview	Sep 24, 2026 2:52am UTC

renovate · 2026-03-26T19:44:00Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: react-beautiful-dnd@13.1.1
npm error Found: react@19.2.4
npm error node_modules/react
npm error   peer react@">=16.8.0" from @emotion/react@11.14.0
npm error   node_modules/@emotion/react
npm error     peer @emotion/react@"^11.0.0-rc.0" from @emotion/styled@11.14.1
npm error     node_modules/@emotion/styled
npm error       peerOptional @emotion/styled@"^11.3.0" from @mui/lab@7.0.1-beta.23
npm error       node_modules/@mui/lab
npm error         @mui/lab@"^7.0.1-beta.19" from the root project
npm error       4 more (@mui/material, @mui/styled-engine, @mui/system, the root project)
npm error     peerOptional @emotion/react@"^11.5.0" from @mui/lab@7.0.1-beta.23
npm error     node_modules/@mui/lab
npm error       @mui/lab@"^7.0.1-beta.19" from the root project
npm error     5 more (@mui/material, @mui/styled-engine, @mui/system, ...)
npm error   peer react@">=16.8.0" from @emotion/styled@11.14.1
npm error   node_modules/@emotion/styled
npm error     peerOptional @emotion/styled@"^11.3.0" from @mui/lab@7.0.1-beta.23
npm error     node_modules/@mui/lab
npm error       @mui/lab@"^7.0.1-beta.19" from the root project
npm error     peerOptional @emotion/styled@"^11.3.0" from @mui/material@7.3.9
npm error     node_modules/@mui/material
npm error       peer @mui/material@"^7.3.9" from @mui/icons-material@7.3.9
npm error       node_modules/@mui/icons-material
npm error         @mui/icons-material@"^7.3.5" from the root project
npm error       2 more (@mui/lab, the root project)
npm error     3 more (@mui/styled-engine, @mui/system, the root project)
npm error   31 more (@emotion/use-insertion-effect-with-fallbacks, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8.5 || ^17.0.0 || ^18.0.0" from react-beautiful-dnd@13.1.1
npm error node_modules/react-beautiful-dnd
npm error   react-beautiful-dnd@"^13.1.1" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error   peer react@"^16.8.5 || ^17.0.0 || ^18.0.0" from react-beautiful-dnd@13.1.1
npm error   node_modules/react-beautiful-dnd
npm error     react-beautiful-dnd@"^13.1.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-24T02_49_00_658Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-24T02_49_00_658Z-debug-0.log

renovate Bot added dependencies renovate labels Mar 26, 2026

vercel Bot deployed to Preview March 26, 2026 17:50 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from 650ec39 to 7346ece Compare March 26, 2026 19:43

vercel Bot deployed to Preview March 26, 2026 19:46 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from 7346ece to 2f68d7d Compare March 27, 2026 08:27

renovate Bot changed the title ~~Update dependency posthog-node to v5.28.6~~ Update dependency posthog-node to v5.28.7 Mar 27, 2026

vercel Bot deployed to Preview March 27, 2026 08:29 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from 2f68d7d to 05189fc Compare March 27, 2026 17:57

renovate Bot changed the title ~~Update dependency posthog-node to v5.28.7~~ Update dependency posthog-node to v5.28.8 Mar 27, 2026

vercel Bot deployed to Preview March 27, 2026 18:00 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from 05189fc to 0a61d5e Compare March 28, 2026 00:39

vercel Bot deployed to Preview March 28, 2026 00:40 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from 0a61d5e to de8ef70 Compare March 30, 2026 16:50

renovate Bot changed the title ~~Update dependency posthog-node to v5.28.8~~ Update dependency posthog-node to v5.28.9 Mar 30, 2026

vercel Bot deployed to Preview March 30, 2026 16:52 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from de8ef70 to b262314 Compare April 1, 2026 20:10

renovate Bot changed the title ~~Update dependency posthog-node to v5.28.9~~ Update dependency posthog-node to v5.28.10 Apr 1, 2026

vercel Bot deployed to Preview April 1, 2026 20:13 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from b262314 to 1bdaf2c Compare April 2, 2026 08:57

renovate Bot changed the title ~~Update dependency posthog-node to v5.28.10~~ Update dependency posthog-node to v5.28.11 Apr 2, 2026

vercel Bot deployed to Preview April 2, 2026 08:59 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from 1bdaf2c to 2c8de79 Compare April 7, 2026 09:41

renovate Bot changed the title ~~Update dependency posthog-node to v5.28.11~~ Update dependency posthog-node to v5.29.0 Apr 7, 2026

vercel Bot deployed to Preview April 7, 2026 09:43 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from 2c8de79 to 04b0491 Compare April 8, 2026 01:50

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from 6b2dac9 to e6b3e90 Compare April 23, 2026 10:52

renovate Bot changed the title ~~Update dependency posthog-node to v5.29.5~~ Update dependency posthog-node to v5.29.6 Apr 23, 2026

vercel Bot deployed to Preview April 23, 2026 10:54 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from e6b3e90 to d278f67 Compare April 23, 2026 17:03

renovate Bot changed the title ~~Update dependency posthog-node to v5.29.6~~ Update dependency posthog-node to v5.29.7 Apr 23, 2026

vercel Bot deployed to Preview April 23, 2026 17:05 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from d278f67 to efb3ad4 Compare April 23, 2026 22:45

renovate Bot changed the title ~~Update dependency posthog-node to v5.29.7~~ Update dependency posthog-node to v5.30.0 Apr 23, 2026

vercel Bot deployed to Preview April 23, 2026 22:47 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from efb3ad4 to f5993b8 Compare April 24, 2026 10:45

renovate Bot changed the title ~~Update dependency posthog-node to v5.30.0~~ Update dependency posthog-node to v5.30.1 Apr 24, 2026

vercel Bot deployed to Preview April 24, 2026 10:47 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from f5993b8 to ec08cdf Compare April 24, 2026 17:53

renovate Bot changed the title ~~Update dependency posthog-node to v5.30.1~~ Update dependency posthog-node to v5.30.3 Apr 24, 2026

vercel Bot deployed to Preview April 24, 2026 17:55 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from ec08cdf to 04701c6 Compare April 24, 2026 21:24

renovate Bot changed the title ~~Update dependency posthog-node to v5.30.3~~ Update dependency posthog-node to v5.30.4 Apr 24, 2026

vercel Bot deployed to Preview April 24, 2026 21:26 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from 04701c6 to 57b4202 Compare April 27, 2026 11:16

renovate Bot changed the title ~~Update dependency posthog-node to v5.30.4~~ Update dependency posthog-node to v5.30.5 Apr 27, 2026

vercel Bot deployed to Preview April 27, 2026 11:17 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from 57b4202 to 28b6747 Compare April 27, 2026 19:48

renovate Bot changed the title ~~Update dependency posthog-node to v5.30.5~~ Update dependency posthog-node to v5.30.6 Apr 27, 2026

vercel Bot deployed to Preview April 27, 2026 19:49 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from 28b6747 to 65a44af Compare April 29, 2026 11:38

renovate Bot changed the title ~~Update dependency posthog-node to v5.30.6~~ Update dependency posthog-node to v5.30.8 Apr 29, 2026

vercel Bot deployed to Preview April 29, 2026 11:40 View deployment

renovate Bot force-pushed the renovate/posthog-node-5.x-lockfile branch from 65a44af to 7794160 Compare April 29, 2026 20:43

renovate Bot changed the title ~~Update dependency posthog-node to v5.30.8~~ Update dependency posthog-node to v5.31.0 Apr 29, 2026

Update dependency posthog-node to v5.53.0

5954c39

Navigation Menu

Update dependency posthog-node to v5.53.0 - #318

Update dependency posthog-node to v5.53.0#318
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/posthog-node-5.x-lockfile

renovate Bot commented Mar 26, 2026 •

edited

Loading

Uh oh!

vercel Bot commented Mar 26, 2026 •

edited

Loading

Uh oh!

renovate Bot commented Mar 26, 2026 •

edited

Loading

Uh oh!

This branch was successfully deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Mar 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Configuration

Uh oh!

vercel Bot commented Mar 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

renovate Bot commented Mar 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ Artifact update problem

File name: package-lock.json

Uh oh!

This branch was successfully deployed

Reviewers

Assignees

Labels

Projects

renovate Bot commented Mar 26, 2026 •

edited

Loading

vercel Bot commented Mar 26, 2026 •

edited

Loading

renovate Bot commented Mar 26, 2026 •

edited

Loading