Skip to content

chore(deps): bump github.com/posthog/posthog-go from 1.8.2 to 1.11.3#629

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/go_modules/github.com/posthog/posthog-go-1.11.3
Open

chore(deps): bump github.com/posthog/posthog-go from 1.8.2 to 1.11.3#629
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/go_modules/github.com/posthog/posthog-go-1.11.3

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Apr 14, 2026

Bumps github.com/posthog/posthog-go from 1.8.2 to 1.11.3.

Release notes

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

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

v1.11.1

1.11.1 - 2026-03-11

v1.10.0

1.10.0 - 2026-02-04

New Features

  • GetFeatureFlagResult: New method that returns both the flag value and payload in a single call, while properly tracking feature flag usage via $feature_flag_called events.

Deprecations

  • GetFeatureFlagPayload: Deprecated in favor of GetFeatureFlagResult. The new method provides better tracking and a more convenient API.

Migration Guide

// Before (two calls, no event tracking for payload-only):
flag, _ := client.GetFeatureFlag(payload)
payloadStr, _ := client.GetFeatureFlagPayload(payload)
// After (single call, always tracks):
result, err := client.GetFeatureFlagResult(payload)
if err != nil { /* handle */ }
if result.Enabled {
var config MyConfig
result.GetPayloadAs(&config)
}

Note: GetFeatureFlagResult returns nil, error when a flag doesn't exist (rather than a result with Enabled: false). Check for errors to distinguish between a disabled flag and a missing flag:

result, err := client.GetFeatureFlagResult(payload)
</tr></table> 

... (truncated)

Changelog

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

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.

1.11.2 - 2026-03-26

1.11.1 - 2026-03-11

1.10.0 - 2026-02-04

New Features

  • GetFeatureFlagResult: New method that returns both the flag value and payload in a single call, while properly tracking feature flag usage via $feature_flag_called events.

Deprecations

  • GetFeatureFlagPayload: Deprecated in favor of GetFeatureFlagResult. The new method provides better tracking and a more convenient API.

Migration Guide

// Before (two calls, no event tracking for payload-only):
flag, _ := client.GetFeatureFlag(payload)
payloadStr, _ := client.GetFeatureFlagPayload(payload)
// After (single call, always tracks):
result, err := client.GetFeatureFlagResult(payload)
if err != nil { /* handle */ }
if result.Enabled {
var config MyConfig
result.GetPayloadAs(&config)
}

Note: GetFeatureFlagResult returns nil, error when a flag doesn't exist (rather than a result with Enabled: false). Check for errors to distinguish between a disabled flag and a missing flag:

result, err := client.GetFeatureFlagResult(payload)
if errors.Is(err, posthog.ErrFlagNotFound) {
    // Flag doesn't exist - use default behavior
}
if err != nil {
</tr></table> 

... (truncated)

Commits
  • 0da2e52 chore: bump version to 1.11.3 [version bump]
  • e545f21 feat: add locally_evaluated property to $feature_flag_called (#176)
  • 5cdecbe chore: add GitHub community health files (#177)
  • 158fd47 chore: add stale workflow for issues and PRs (#175)
  • 582bcf4 chore: bump version to 1.11.2 [version bump]
  • deed4e0 chore: update release workflow action versions (#173)
  • 2a75905 fix: dramatically reduce memory allocations in feature flag evaluation (#172)
  • a9cb449 chore: extract releasing docs and add PR template (#171)
  • 3ea4481 feat: add automatic system context to all events (#167)
  • 5846581 fix: target master branch in CodeQL workflow (#170)
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [github.com/posthog/posthog-go](https://github.com/posthog/posthog-go) from 1.8.2 to 1.11.3.
- [Release notes](https://github.com/posthog/posthog-go/releases)
- [Changelog](https://github.com/PostHog/posthog-go/blob/main/CHANGELOG.md)
- [Commits](PostHog/posthog-go@v1.8.2...v1.11.3)

---
updated-dependencies:
- dependency-name: github.com/posthog/posthog-go
  dependency-version: 1.11.3
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Apr 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants