Bump the go-minor-patch group across 1 directory with 2 updates

[dependabot]

Bumps the go-minor-patch group with 2 updates in the /apps/api directory: github.com/posthog/posthog-go and github.com/pressly/goose/v3.

Updates github.com/posthog/posthog-go from 1.17.5 to 1.22.0

Release notes

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

1.22.0

Unreleased

1.21.0

Unreleased

1.20.0

Unreleased

1.19.0

Unreleased

1.18.0

Unreleased

Changelog

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

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.

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.

Commits

• 6b63077 chore: release v1.22.0 [version bump] [skip ci]
• f102f70 feat(error-tracking): grouped inline frames + debug images for server-side sy...
• 73399d9 chore: release v1.21.0 [version bump] [skip ci]
• 9e9ad63 feat(flags): minimize $feature_flag_called events for non-experiment flags (#...
• 10bec86 chore: release v1.20.0 [version bump] [skip ci]
• 3ea8ce6 feat: send error tracking stack frames in canonical bottom-up order (#254)
• 901880f chore: release v1.19.0 [version bump] [skip ci]
• 154fd08 feat(flags): add $feature_flag_has_experiment to $feature_flag_called events ...
• 9e7c67e chore: release v1.18.0 [version bump] [skip ci]
• 39c72dc feat: drop newest on full queue, add configurable MaxQueueSize (#258)
• Additional commits viewable in compare view

Updates github.com/pressly/goose/v3 from 3.27.2 to 3.27.3

Release notes

Sourced from github.com/pressly/goose/v3's releases.

v3.27.3

Changed

• Various dependency upgrades

Changelog

Sourced from github.com/pressly/goose/v3's changelog.

[v3.27.3] - 2026-07-22

Changed

• Various dependency upgrades

Commits

• 520411a release: v3.27.3
• 26403f9 build(deps): update internal/testing dependencies
• abcfbd1 ci: pin GitHub Actions to commit SHAs
• a54dd54 build(deps): bump actions/setup-go from 6 to 7 (#1094)
• 27c2f4f build(deps): update dependencies
• a443d13 fix: capture markdown subsections in release-notes.sh
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions