Bump github.com/posthog/posthog-go from 0.0.0-20230801140217-d607812dee69 to 1.24.3

[dependabot]

Bumps github.com/posthog/posthog-go from 0.0.0-20230801140217-d607812dee69 to 1.24.3.

Release notes

Sourced from github.com/posthog/posthog-go's releases.

1.24.3

Unreleased

1.24.2

Unreleased

1.24.1

Unreleased

1.24.0

Unreleased

1.23.1

Unreleased

1.23.0

Unreleased

1.22.0

Unreleased

1.21.0

Unreleased

1.20.0

Unreleased

1.19.0

Unreleased

1.18.0

Unreleased

1.17.5

Unreleased

1.17.4

Unreleased

1.17.3

Unreleased

1.17.2

Unreleased

1.17.1

Unreleased

1.17.0

Unreleased

... (truncated)

Changelog

Sourced from github.com/posthog/posthog-go's changelog.

1.24.3

Patch Changes

• 749f1e8: Fix exact/is_not local flag evaluation to match case-insensitively and after string coercion, consistent with the other string operators here and the reference SDKs. A plain Go == made them case- and type-sensitive, so e.g. exact "US" did not match a "us" property value and exact 1 did not match a "1" property value.

1.24.2

Patch Changes

• 360bc8d: Align local is_set and is_not_set evaluation with partial property context.

1.24.1

Patch Changes

• 3d250c5: Return an empty feature flag snapshot without evaluating flags when FlagKeys is an explicit empty slice.

1.24.0

Minor Changes

• 150f03e: Fall back to /flags when a requested flag is missing from loaded local definitions. This changes the earlier behavior where the key was omitted without a request.

1.23.1

Patch Changes

• ec8f6c0: Normalize event timestamps to the equivalent UTC instant before serializing legacy batch and Capture V1 payloads.

1.23.0

Minor Changes

• 941d9ca: 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.

1.22.0

Minor Changes

• f102f70: Error tracking stack traces now support server-side symbolication. When the running executable's identity can be determined (GNU build id on Linux, LC_UUID on macOS), the default extractor emits frames with raw instruction addresses and client-expanded inline groups, and exceptions carry a $debug_images property, so PostHog can re-symbolicate against debug symbols uploaded with posthog-cli symbol-sets upload — including exact inline expansion and source context. Without uploaded symbols the runtime-resolved frames are kept as-is, and when the executable can't be identified the frames keep their previous plain shape.

  Requires a PostHog backend with grouped inline frame support (PostHog Cloud, or self-hosted ≥ July 2026). Older backends resolve each group member independently, which duplicates inline expansions when debug symbols are uploaded. To keep the previous plain frames, use a custom StackTraceExtractor.

1.21.0

Minor Changes

• 9e9ad63: Send minimal $feature_flag_called events when the server enables it. When the /flags?v=2 response carries minimalFlagCalledEvents: true (remote evaluation) or the local-evaluation definitions payload carries minimal_flag_called_events: true, and the evaluated flag has has_experiment: false, the event keeps only a strict allowlist of evaluation properties ($feature_flag, $feature_flag_response, $feature_flag_has_experiment, $feature_flag_id, $feature_flag_version, $feature_flag_reason, $feature_flag_request_id, $feature_flag_evaluated_at, $feature_flag_error, locally_evaluated, $groups, $process_person_profile, $geoip_disable, $is_server, $session_id, $window_id, $device_id, $lib, $lib_version) plus static system context ($os, $os_version, $os_distro, $go_version); everything else — including Config.DefaultEventProperties and the snapshot path's $feature/<key> and $feature_flag_payload — is stripped. Any missing signal (gate absent, has_experiment unknown, experiment-linked flag, legacy response shapes) keeps today's full event shape. The gate is server-controlled per project; no SDK configuration is added.

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
🔚	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.