Skip to content

chore(deps): bump posthog-js to ^1.433.4 - #2

Draft
posthog[bot] wants to merge 1 commit into
masterfrom
posthog-self-driving/choredeps-bump-posthog-js-from-14225-to-8f889a
Draft

posthog[bot] wants to merge 1 commit into
masterfrom
posthog-self-driving/choredeps-bump-posthog-js-from-14225-to-8f889a

Conversation

@posthog

@posthog posthog Bot commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

Problem

  • The morning posthog-js bump merged already stale: master pinned ^1.422.5 (lockfile 1.422.5) while npm's current release is 1.433.4 — 11 releases behind.
  • Nobody is broken: tracking works, no error-tracking issues. Old-version events are cached bundles on visitor machines that turn over on their own, since this is a static site and posthog-js ships inside the built JS.
  • The real cost is recurrence: each bump lands behind, so the SDK health check keeps firing on the same lag.

Changes

  • Bump posthog-js to ^1.433.4 and refresh package-lock.json.
  • No call-site change. src/components/Analytics.astro uses only posthog.init and posthog.capture, both stable across these releases.

Verification

  • npm run build — passed
  • make check — passed
  • npm test — 136 tests passed

Created with PostHog Desktop from this inbox report.

🤖 Generated with Claude Code

Update posthog-js from 1.422.5 to 1.433.4 to keep the analytics SDK
current. Only posthog.init and posthog.capture are used in
src/components/Analytics.astro, both stable across these releases, so no
call-site change is needed.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Generated-By: PostHog Desktop
Task-Id: 36e59225-37aa-47e3-98bd-1aa85d2ce4a8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant