chore: bump posthog-telemetry to f550a66 (Error Tracking fix) - #250
Merged
Conversation
Pulls in DataZooDE/posthog-telemetry#10: CaptureError() now emits $exception_list + a product-scoped $exception_fingerprint so PostHog Error Tracking actually creates issues (events were previously rejected at ingestion with 'missing field $exception_list'). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pulls in DataZooDE/posthog-telemetry#10 — CaptureError() now stamps $exception_list ([{type,value}] = error_class, no stack by design) and a product-scoped $exception_fingerprint (/<error_class>); previously every $exception event was rejected by PostHog ingestion ('missing field $exception_list') so no Error Tracking issues were created. Submodule fast-forward only, no API changes.
Local verification
Worktree at .bump-worktrees/anofox-forecast already had the bump commit (76bc2b2 "chore: bump posthog-telemetry to f550a66") from a prior partial run, correctly pointing posthog-telemetry gitlink at f550a663d491e29b521998a9c1ca63bb6503c83a on top of origin/main. No open PR existed yet for chore/bump-posthog-telemetry-f550a66 and origin/main was still on the old submodule commit, so this run proceeded to the BUILD step. Ran
GEN=ninja CORES=8 CMAKE_BUILD_PARALLEL_LEVEL=8 make release(vcpkg toolchain).🤖 Generated with Claude Code
Need help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.