Skip to content

chore: bump github.com/posthog/posthog-go from 1.9.1 to 1.10.0#827

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

chore: bump github.com/posthog/posthog-go from 1.9.1 to 1.10.0#827
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/go_modules/github.com/posthog/posthog-go-1.10.0

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 5, 2026

Bumps github.com/posthog/posthog-go from 1.9.1 to 1.10.0.

Release notes

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

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)
if errors.Is(err, posthog.ErrFlagNotFound) {
    // Flag doesn't exist - use default behavior
}
if err != nil {
    // Other error (e.g., network issue)
}
if result.Enabled {
    // Flag exists and is enabled
} else {
    // Flag exists but is disabled
}
Changelog

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

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 {
    // Other error (e.g., network issue)
}
if result.Enabled {
    // Flag exists and is enabled
} else {
    // Flag exists but is disabled
}
Commits
  • c5bb4da chore: bump version to 1.10.0 [version bump]
  • 3fc9731 feat: Add device_id parameter to /flags requests (#157)
  • 634f3b8 fix(flags): avoid setting flags to false on transient errors (#162)
  • 7ae0fe8 fix: Flag payloads can contain JSON types (#161)
  • 945f3c8 feat: Add GetFeatureFlagResult method to client (#159)
  • 3539620 ci: Validate go fmt has been run (#160)
  • 3335d4d Trivial: Remove leading $ from go get command, so it doesn't get copied autom...
  • ec17963 feat: SDK Compliance (#150)
  • See full diff 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)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Feb 5, 2026
@dependabot dependabot bot requested a review from a team as a code owner February 5, 2026 19:03
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Feb 5, 2026
Bumps [github.com/posthog/posthog-go](https://github.com/posthog/posthog-go) from 1.9.1 to 1.10.0.
- [Release notes](https://github.com/posthog/posthog-go/releases)
- [Changelog](https://github.com/PostHog/posthog-go/blob/master/CHANGELOG.md)
- [Commits](PostHog/posthog-go@v1.9.1...v1.10.0)

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/posthog/posthog-go-1.10.0 branch from dde8829 to 6b40b2a Compare February 26, 2026 19:03
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