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

[dependabot]

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

Release notes

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

1.13.2

Unreleased

1.13.1

Unreleased

1.13.0

Unreleased

1.12.6

Unreleased

1.12.5

Unreleased

1.12.4 - 2026-04-30

• Full Changelog

1.12.3 - 2026-04-21

• Full Changelog

1.12.2 - 2026-04-20

• Full Changelog

v1.12.1

1.12.1 - 2026-04-20

• Full Changelog

v1.12.0

1.12.0 - 2026-04-20

• Full Changelog

v1.11.3

1.11.3 - 2026-04-14

• Full Changelog

• Added locally_evaluated property to $feature_flag_called events, indicating whether the flag was evaluated locally or via the remote /flags endpoint.

v1.11.2

1.11.2 - 2026-03-26

• Full Changelog

v1.11.1

... (truncated)

Changelog

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

1.13.2

Patch Changes

• df2ae97: Capture with SendFeatureFlags(true) now prefers local evaluation when flag definitions are loaded, falling back to a remote /flags request only for flags that can't be computed locally. OnlyEvaluateLocally remains strictly local with no remote fallback.

  Captured events now exclude flags that evaluate to false from $active_feature_flags (they are still attached as $feature/<key>=false), matching the other PostHog SDKs.

1.13.1

Patch Changes

• 541b82f: Include group context in the $feature_flag_called LRU dedupe key so group-scoped flags fire a separate event for each group a user is evaluated under, instead of being dedup-ed against the first group context the same (distinct_id, flag, device_id) was seen under.

1.13.0

Minor Changes

• dec8ade: Add opt-in panic capture for request context middleware.
• dec8ade: Add server-side request context helpers for net/http capture and exception events, plus EvaluateFlagsWithContext for using request-scoped distinct IDs during flag evaluation. Request-context flag evaluation does not generate personless IDs.

1.12.6

Patch Changes

• 9289d53: 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 an InconclusiveMatchError so the condition does not match.

1.12.5

Patch Changes

• 6d243a6: Return ErrSDKDisabled from no-op clients when the project API key is missing, return ErrNoPersonalAPIKey before making requests for Personal API key dependent methods when no Personal API key is configured, and return ErrNoDistinctID from EvaluateFlags when distinct_id is missing.

New Features

• EvaluateFlags: New method on Client that returns a FeatureFlagEvaluations snapshot for a user using a single /flags request. The snapshot powers any number of IsEnabled / GetFlag / GetFlagPayload checks, fires deduped $feature_flag_called events with full v4 metadata (id, version, reason, request_id), and can be attached to a Capture event via the new Capture.Flags field to populate $feature/<key> and $active_feature_flags without another network call.
• Capture.Flags: New optional field on Capture that accepts a *FeatureFlagEvaluations snapshot. Takes precedence over SendFeatureFlags, avoids a hidden /flags request per event, and lets caller-supplied Properties override the auto-generated $feature/<key> values on conflict.

Internal

• Refactored the $feature_flag_called dedup logic into a shared helper so the existing single-flag path and the new snapshot path use identical semantics against the same per-distinct_id LRU cache.
• $feature_flag_called events from the snapshot path combine response-level errors (errors_while_computing_flags, quota_limited) with per-flag errors (flag_missing) comma-joined in $feature_flag_error, matching the granularity of the legacy single-flag path.

1.12.4 - 2026-04-30

• Full Changelog

1.12.3 - 2026-04-21

• Full Changelog

... (truncated)

Commits

• See full diff in compare view

[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
✅	Code Security	0	0	0	0	0 issues

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