Skip to content

chore(deps): update dependency posthog-node to v5 - #2962

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/posthog-node-5.x
Open

chore(deps): update dependency posthog-node to v5#2962
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/posthog-node-5.x

Conversation

@renovate

@renovate renovate Bot commented Aug 11, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
posthog-node (source) ^4.18.0 → ^5.48.1 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

PostHog/posthog-js (posthog-node)

v5.48.1

Compare Source

Patch Changes

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

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]:

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

v5.47.7

Compare Source

Patch Changes

v5.47.6

Compare Source

Patch Changes

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]:

v5.47.4

Compare Source

Patch Changes

v5.47.3

Compare Source

Patch Changes

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]:

v5.47.1

Compare Source

Patch Changes

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

v5.46.1

Compare Source

Patch Changes

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

v5.45.2

Compare Source

Patch Changes

v5.45.1

Compare Source

Patch Changes

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

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

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

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

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

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

v5.39.3

Compare Source

Patch Changes

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]:

v5.39.1

Compare Source

Patch Changes

v5.39.0

Compare Source

Minor Changes
  • #​4006 0063128 Thanks @​github-actions! - Add groupIdentifyImmediate() to await the network request when identifying a group, mirroring captureImmediate/identifyImmediate/aliasImmediate. Useful in edge/serverless environments where the background queue may not flush. The Convex integration now uses it directly instead of routing $groupidentify through captureImmediate.
    (2026-06-30)
Patch Changes

v5.38.8

Compare Source

Patch Changes
  • #​3974 08b404b Thanks @​mjfaga! - Fix local evaluation ignoring the in/not_in operator on cohort-based flag conditions. "Not in
    cohort" was evaluated as "in cohort", inverting cohort-exclusion flags. Now applies the operator to
    the cohort membership result. (2026-06-29)

v5.38.7

Compare Source

Patch Changes
  • #​3961 619a25c Thanks @​marandaneto! - Retry feature flag requests after transient network errors only. The feature flag request retry count defaults to 1 and can be set to 0 to disable retries.
    (2026-06-29)
  • Updated dependencies [619a25c]:

v5.38.6

Compare Source

Patch Changes

v5.38.5

Compare Source

Patch Changes

v5.38.4

Compare Source

Patch Changes

v5.38.3

Compare Source

Patch Changes

v5.38.2

Compare Source

Patch Changes

v5.38.1

Compare Source

Patch Changes
  • #​3886 e6d7fe2 Thanks @​marandaneto! - Stop sending deprecated no-op top-level type, library, and library_version fields in event batch payloads. Use properties.$lib and properties.$lib_version for SDK metadata; legacy queued library and library_version values are used as fallbacks when the official $ properties are missing.
    (2026-06-18)
  • Updated dependencies [e6d7fe2]:

v5.38.0

Compare Source

Minor Changes
  • #​3845 a0553b3 Thanks @​marandaneto! - Add setPersonProperties() and unsetPersonProperties() helpers to manage person properties from the Node.js SDK.
    (2026-06-16)
Patch Changes

v5.37.1

Compare Source

Patch Changes

v5.37.0

Compare Source

Minor Changes
  • #​3705 d6fc0a5 Thanks @​gustavohstrassburger! - feat(feature-flags): support the early_exit condition option in local evaluation. When a flag enables early exit, evaluation now stops and returns false as soon as a condition group's property filters match but the rollout percentage excludes the user, instead of falling through to later groups — matching the server-side evaluation behavior.
    (2026-06-12)

v5.36.17

Compare Source

Patch Changes

v5.36.16

Compare Source

Patch Changes

v5.36.15

Compare Source

Patch Changes

v5.36.14

Compare Source

Patch Changes

v5.36.13

Compare Source

Patch Changes

v5.36.12

Compare Source

Patch Changes

v5.36.11

Compare Source

Patch Changes

v5.36.10

Compare Source

Patch Changes

v5.36.9

Compare Source

Patch Changes

v5.36.8

Compare Source

Patch Changes

v5.36.7

Compare Source

Patch Changes

v5.36.6

Compare Source

Patch Changes

v5.36.5

Compare Source

Patch Changes

v5.36.4

Compare Source

Patch Changes

v5.36.3

Compare Source

Patch Changes

v5.36.2

Compare Source

Patch Changes

v5.36.1

Compare Source

Patch Changes

v5.36.0

Compare Source

Minor Changes
  • #​3728 9287c87 Thanks @​turnipdabeets! - Add a configurable $is_server event property (default true) so PostHog can identify server-side events. Set isServer: false when using the SDK as a client/CLI so the device OS is attributed normally.
    (2026-06-04)

v5.35.15

Compare Source

Patch Changes

v5.35.14

Compare Source

Patch Changes

v5.35.13

Compare Source

Patch Changes

v5.35.12

Compare Source

Patch Changes

v5.35.11

Compare Source

Patch Changes

v5.35.10

Compare Source

Patch Changes

v5.35.9

Compare Source

Patch Changes

v5.35.8

Compare Source

Patch Changes

v5.35.7

Compare Source

Patch Changes

v5.35.6

Compare Source

Patch Changes

v5.35.5

Compare Source

Patch Changes

v5.35.4

Compare Source

Patch Changes

v5.35.3

Compare Source

Patch Changes

v5.35.2

Compare Source

Patch Changes
  • #​3658 5d7a2d3 Thanks @​gustavohstrassburger! - Include group context in the $feature_flag_called deduplication key in _captureFlagCalledEventIfNeeded, so events fire independently per group combination.
    (2026-05-25)

v5.35.1

Compare Source

Patch Changes

v5.35.0

Compare Source

Minor Changes
  • #​3642 18ea8b5 Thanks @​dustinbyrne! - Promote feature flag definition cache provider types to the main posthog-node export and deprecate posthog-node/experimental imports.
    (2026-05-21)
Patch Changes

v5.34.10

Compare Source

Patch Changes
  • #​3643 f42f371 Thanks @​dmarticus! - Reject semver values with leading zeros in local flag evaluation. Per semver 2.0.0 §2, numeric identifiers must not include leading zeros — values like 1.07.3 are not valid semver and should not match targeting conditions. Both override values and flag values are now validated; invalid inputs surface as InconclusiveMatchError so the condition does not match.
    (2026-05-21)

v5.34.9

Compare Source

Patch Changes

v5.34.8

Compare Source

Patch Changes
  • #​3640 12ef3f6 Thanks @​hpouillot! - Fix identifyImmediate to await the underlying network request. Previously the returned promise resolved before the $identify event was sent, causing events to be dropped when called from short-lived runtimes (Vercel/Cloudflare Workers, Convex actions) that exit immediately after await.
    (2026-05-21)

v5.34.7

Compare Source

Patch Changes

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

@coolify-skkuding

coolify-skkuding Bot commented Aug 11, 2025 •
edited
Loading

Copy link
Copy Markdown

The preview deployment is ready. 🟢

Open Preview | Open Build Logs

Last updated at: 2025-08-27 10:21:49 CET

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from b3a8f87 to de239ca Compare August 11, 2025 08:06
@skkuding-bot

skkuding-bot Bot commented Aug 12, 2025

Copy link
Copy Markdown

❗ Syncing Preview App Failed

Application: frontend
Revision: de239ca432f67d31fdb7fb0f4b22c93cc06e1aba
Health Status: Missing

Open Preview | View in Argo CD

@skkuding-bot

skkuding-bot Bot commented Aug 13, 2025

Copy link
Copy Markdown

❗ Syncing Preview App Failed

Application: frontend
Revision: de239ca432f67d31fdb7fb0f4b22c93cc06e1aba
Health Status: Degraded

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from de239ca to 52df174 Compare August 13, 2025 14:04
@skkuding-bot

skkuding-bot Bot commented Aug 13, 2025

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: 52df17458055934965925cf9c82850a293e8582f
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from 52df174 to d4a063d Compare August 14, 2025 14:03
@skkuding-bot

skkuding-bot Bot commented Aug 14, 2025

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: d4a063d5137bf489f4ac12d683865af48e9fff29
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from d4a063d to f2083ca Compare August 15, 2025 16:02
@skkuding-bot

skkuding-bot Bot commented Aug 15, 2025

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: f2083cacf439724483c211609dc6f255910f9c55
Health Status: Healthy

Open Preview | View in Argo CD

@skkuding-bot

skkuding-bot Bot commented Aug 17, 2025

Copy link
Copy Markdown

❗ Syncing Preview App Failed

Application: frontend
Revision: f2083cacf439724483c211609dc6f255910f9c55
Health Status: Missing

Open Preview | View in Argo CD

@skkuding-bot

skkuding-bot Bot commented Aug 17, 2025

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: f2083cacf439724483c211609dc6f255910f9c55
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from f2083ca to cc13337 Compare August 19, 2025 11:34
@skkuding-bot

skkuding-bot Bot commented Aug 19, 2025

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: cc133371612d5167fc94a9de3e05b8b87549635a
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from cc13337 to 5c930f5 Compare August 26, 2025 09:53
@skkuding-bot

skkuding-bot Bot commented Aug 26, 2025

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: 5c930f5795722a5a6252a101c9e9c9f21a66b262
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from 5c930f5 to 9f38b1b Compare August 27, 2025 10:16
@skkuding-bot

skkuding-bot Bot commented Aug 27, 2025

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: 9f38b1b2b85f7aa46034fd1a99a160ad65e4ccf9
Health Status: Healthy

Open Preview | View in Argo CD

1 similar comment
@skkuding-bot

skkuding-bot Bot commented Aug 30, 2025

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: 9f38b1b2b85f7aa46034fd1a99a160ad65e4ccf9
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from 9f38b1b to d64c808 Compare August 31, 2025 09:54
@skkuding-bot

skkuding-bot Bot commented Aug 31, 2025

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: d64c80815ea1b2678ebc599ef90ee468bd2747c7
Health Status: Healthy

Open Preview | View in Argo CD

@skkuding-bot

skkuding-bot Bot commented Sep 1, 2025

Copy link
Copy Markdown

❗ Syncing Preview App Failed

Application: frontend
Revision: <no value>
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from d64c808 to 6482037 Compare September 5, 2025 03:15
@skkuding-bot

skkuding-bot Bot commented Sep 5, 2025

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: 64820378fe1fc141b0c074fcb5fa75377618ad83
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from 6482037 to 23dacaa Compare September 11, 2025 01:51
@skkuding-bot

skkuding-bot Bot commented Sep 11, 2025

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: 23dacaa41e592c88c74da9e43cba694cfb862390
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from 23dacaa to 5928fc9 Compare September 11, 2025 19:16
@skkuding-bot

skkuding-bot Bot commented Sep 11, 2025

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: 5928fc9cfb7e00f802280f8b1c4b543c19702b6f
Health Status: Healthy

Open Preview | View in Argo CD

1 similar comment
@skkuding-bot

skkuding-bot Bot commented Sep 12, 2025

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: 5928fc9cfb7e00f802280f8b1c4b543c19702b6f
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from 93d7ba8 to a462c88 Compare December 21, 2025 00:15
@skkuding-bot

skkuding-bot Bot commented Dec 21, 2025

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: a462c88802feb865ff4a23bfda343a07a7723f60
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from a462c88 to 7580287 Compare December 22, 2025 18:56
@skkuding-bot

skkuding-bot Bot commented Dec 22, 2025

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: 75802873c44bc41493088f06b57b737d256488aa
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from 7580287 to 0764bf9 Compare January 4, 2026 20:25
@skkuding-bot

skkuding-bot Bot commented Jan 4, 2026

Copy link
Copy Markdown

❗ Syncing Preview App Failed

Application: frontend
Revision: 0764bf90d25aa5cae8fdf98612eec15e2268c8e1
Health Status: Degraded

Open Preview | View in Argo CD

@skkuding-bot

skkuding-bot Bot commented Jan 4, 2026

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: 0764bf90d25aa5cae8fdf98612eec15e2268c8e1
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from 0764bf9 to 09b26d9 Compare January 11, 2026 11:51
@skkuding-bot

skkuding-bot Bot commented Jan 11, 2026

Copy link
Copy Markdown

❗ Syncing Preview App Failed

Application: frontend
Revision: 09b26d99a8b07c49da5bca0225cdacb6ec0f5328
Health Status: Degraded

Open Preview | View in Argo CD

@skkuding-bot

skkuding-bot Bot commented Jan 11, 2026

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: 09b26d99a8b07c49da5bca0225cdacb6ec0f5328
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from 09b26d9 to 3cb166a Compare January 25, 2026 16:09
@skkuding-bot

skkuding-bot Bot commented Jan 25, 2026

Copy link
Copy Markdown

❗ Syncing Preview App Failed

Application: frontend
Revision: 3cb166a4870213f10fd3a10301cf86f66ef2827e
Health Status: Degraded

Open Preview | View in Argo CD

@skkuding-bot

skkuding-bot Bot commented Jan 25, 2026

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: 3cb166a4870213f10fd3a10301cf86f66ef2827e
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from 3cb166a to ba0bf22 Compare January 28, 2026 04:27
@skkuding-bot

skkuding-bot Bot commented Jan 28, 2026

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: ba0bf22a5d9324703b9871e7dea89456b61b8732
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from ba0bf22 to 337c6be Compare February 1, 2026 11:04
@skkuding-bot

skkuding-bot Bot commented Feb 1, 2026

Copy link
Copy Markdown

❗ Syncing Preview App Failed

Application: frontend
Revision: 337c6be77aa18277846e050bad2fd9c2dde24858
Health Status: Healthy

Open Preview | View in Argo CD

@skkuding-bot

skkuding-bot Bot commented Feb 2, 2026

Copy link
Copy Markdown

✅ Syncing Preview App Succeeded

Application: frontend
Revision: 337c6be77aa18277846e050bad2fd9c2dde24858
Health Status: Healthy

Open Preview | View in Argo CD

@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch 4 times, most recently from 3e952d4 to 43f4b1a Compare April 30, 2026 17:33
@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch 2 times, most recently from e96652e to 95527a8 Compare May 5, 2026 06:54
@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch 4 times, most recently from 5ef8829 to e1f8fe5 Compare May 13, 2026 01:26
@renovate
renovate Bot force-pushed the renovate/posthog-node-5.x branch from e1f8fe5 to c09afc4 Compare August 8, 2026 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants