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

[dependabot]

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

Release notes

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

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

1.16.2

Unreleased

1.16.1

Unreleased

1.16.0

Unreleased

1.15.1

Unreleased

1.15.0

Unreleased

1.14.0

Unreleased

1.13.2

Unreleased

... (truncated)

Changelog

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

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.

1.20.0

Minor Changes

• 3ea8ce6: Error tracking stack frames are now sent in the canonical cross-SDK wire order: the entry point is first and the crash/capture site is last. Previously frames were sent innermost-first. Coordinated rollout: the ingestion pipeline gates on $lib_version, so this ships as a minor release.

1.19.0

Minor Changes

• 154fd08: Add a $feature_flag_has_experiment boolean property to $feature_flag_called events. The value comes from the has_experiment field the server reports on flag metadata (/flags?v=2) and on local-evaluation flag definitions. The property is only sent when the server explicitly reported has_experiment (true or false); it is omitted when unknown (older deployments, v3 responses, or flags missing from the response).

1.18.0

Minor Changes

• 39c72dc: Drop the newest event instead of blocking when the in-memory queue is full, and make the queue size configurable.

  • Enqueue now returns ErrQueueFull when the queue is full, dropping the newest message rather than blocking the caller until space frees up. This matches posthog-python and posthog-rs. The drop is reported only through the returned error, not through Callback.Failure, so it stays cheap and off the callback goroutines under sustained overload. Backfill/bulk callers: check the error returned by Enqueue for ErrQueueFull and throttle or retry (or raise MaxQueueSize); otherwise events that overflow the queue are dropped, not delayed.
  • Add Config.MaxQueueSize (default DefaultMaxQueueSize = 10000) to control the in-memory message queue capacity independently of BatchSize. It is clamped up to BatchSize so the queue always holds at least one full batch. This replaces the previous hardcoded BatchSize * 10 sizing.
  • Change the default BatchSize (DefaultBatchSize) from 250 to 100, aligning with posthog-python, posthog-node, and posthog-rs. Callers that set BatchSize explicitly are unaffected.

1.17.5

Patch Changes

• fe66557: Change the default capture delivery budget from 10 attempts to 4 (DefaultMaxAttempts) when Config.MaxRetries is unset, aligning with the cross-SDK Capture V1 parity standard (posthog-rs uses the same envelope). This affects both the v0 (/batch/) and v1 send paths, since they share the attempt budget. Callers that set MaxRetries explicitly are unaffected.
• 3d8404a: Unify the capture retry backoff ceiling at 30s. DefaultBackoff's cap changes from 10s to 30s (default only — override via Config.RetryAfter), and the Capture V1 send now clamps a server Retry-After to the same 30s so a hostile or buggy header cannot park a batch goroutine. Retry-After still acts as a minimum; the configured backoff is never truncated. This aligns the default retry behavior with posthog-rs and posthog-python.

1.17.4

Patch Changes

• 25e43f8: Stop duplicating distinct_id inside /flags person properties.

1.17.3

Patch Changes

• dafed74: Retry remote feature flag requests after transient 502 and 504 responses.

1.17.2

Patch Changes

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