Skip to content

chore(deps): Bump the go-dependencies group in /ssh-reader with 2 updates - #58

Merged
github-actions[bot] merged 1 commit into
mainfrom
dependabot/go_modules/ssh-reader/go-dependencies-47fbb9ae02
Jul 20, 2026
Merged

chore(deps): Bump the go-dependencies group in /ssh-reader with 2 updates#58
github-actions[bot] merged 1 commit into
mainfrom
dependabot/go_modules/ssh-reader/go-dependencies-47fbb9ae02

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 20, 2026

Copy link
Copy Markdown
Contributor

Bumps the go-dependencies group in /ssh-reader with 2 updates: github.com/getsentry/sentry-go and github.com/posthog/posthog-go.

Updates github.com/getsentry/sentry-go from 0.47.0 to 0.48.0

Release notes

Sourced from github.com/getsentry/sentry-go's releases.

0.48.0

Breaking Changes 🛠

New Features ✨

  • Add ClientOptions.DataCollection for granular control over data collected by automatic instrumentation, replacing the broad SendDefaultPII switch. DataCollection can independently configure automatic user.* population, cookies, request/response headers, HTTP bodies, and query parameters. When configured, it is the source of truth and SendDefaultPII is ignored. by @​giortzisg in #1339
    • For backwards compatibility, clients that do not configure DataCollection keep a best-effort mapping of the previous SendDefaultPII behavior. To opt in to the new defaults, pass an empty DataCollection and then restrict individual categories as needed.
    sentry.Init(sentry.ClientOptions{
        Dsn: "https://public@example.com/1",
    // Opt in to the new data collection defaults. Omitted fields use their
    // defaults: user info, cookies, headers, query params, and supported HTTP
    // bodies are collected, with sensitive values filtered.
    DataCollection: &sentry.DataCollection{},
    
    })

    • To opt in while disabling automatic user info and HTTP bodies, configure those fields explicitly:
    sentry.Init(sentry.ClientOptions{
        Dsn: "https://public@example.com/1",
        DataCollection: &sentry.DataCollection{
            UserInfo:   sentry.Set(false),
            HTTPBodies: []sentry.BodyType{},
        },
    })
  • PushScope shorthand now returns the new scope reference by @​DoctorJohn in #1335

Bug Fixes 🐛

Internal Changes 🔧

Deps

... (truncated)

Changelog

Sourced from github.com/getsentry/sentry-go's changelog.

0.48.0

Breaking Changes 🛠

New Features ✨

  • Add ClientOptions.DataCollection for granular control over data collected by automatic instrumentation, replacing the broad SendDefaultPII switch. DataCollection can independently configure automatic user.* population, cookies, request/response headers, HTTP bodies, and query parameters. When configured, it is the source of truth and SendDefaultPII is ignored. by @​giortzisg in #1339
    • For backwards compatibility, clients that do not configure DataCollection keep a best-effort mapping of the previous SendDefaultPII behavior. To opt in to the new defaults, pass an empty DataCollection and then restrict individual categories as needed.
    sentry.Init(sentry.ClientOptions{
        Dsn: "https://public@example.com/1",
    // Opt in to the new data collection defaults. Omitted fields use their
    // defaults: user info, cookies, headers, query params, and supported HTTP
    // bodies are collected, with sensitive values filtered.
    DataCollection: &sentry.DataCollection{},
    
    })

    • To opt in while disabling automatic user info and HTTP bodies, configure those fields explicitly:
    sentry.Init(sentry.ClientOptions{
        Dsn: "https://public@example.com/1",
        DataCollection: &sentry.DataCollection{
            UserInfo:   sentry.Set(false),
            HTTPBodies: []sentry.BodyType{},
        },
    })
  • PushScope shorthand now returns the new scope reference by @​DoctorJohn in #1335

Bug Fixes 🐛

Internal Changes 🔧

Deps

... (truncated)

Commits
  • d02f9ba release: 0.48.0
  • 99c424f feat!: remove issue creation from logging integrations (#1340)
  • d1c1d3f feat: parse request body for outgoing http (#1339)
  • 9b5cab2 fix: fix fiber route name when using middlewares (#1363)
  • 07a7975 fix: omit empty event id for standalone client reports (#1362)
  • c255382 build(deps): bump fiber/v2 to 2.52.14 (#1359)
  • 06c58dc ci: remove changelog-preview and codecov actions (#1357)
  • a99e044 fix: preserve '%' literal in log messages (#1358)
  • 8aaf1d4 feat: apply sensitive data filters to grpc & sql (#1333)
  • 4347773 feat: apply sensitive data filters to http (#1332)
  • Additional commits viewable in compare view

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

Release notes

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

1.19.0

Unreleased

1.18.0

Unreleased

Changelog

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

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
  • 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)
  • d9b6e46 feat: add SecretKey config, deprecate PersonalApiKey (#253)
  • 67f00c8 fix(compliance): retry feature flag requests (#257)
  • 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

Bumps the go-dependencies group in /ssh-reader with 2 updates: [github.com/getsentry/sentry-go](https://github.com/getsentry/sentry-go) and [github.com/posthog/posthog-go](https://github.com/posthog/posthog-go).


Updates `github.com/getsentry/sentry-go` from 0.47.0 to 0.48.0
- [Release notes](https://github.com/getsentry/sentry-go/releases)
- [Changelog](https://github.com/getsentry/sentry-go/blob/master/CHANGELOG.md)
- [Commits](getsentry/sentry-go@v0.47.0...v0.48.0)

Updates `github.com/posthog/posthog-go` from 1.17.5 to 1.19.0
- [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.17.5...v1.19.0)

---
updated-dependencies:
- dependency-name: github.com/getsentry/sentry-go
  dependency-version: 0.48.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-dependencies
- dependency-name: github.com/posthog/posthog-go
  dependency-version: 1.19.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-dependencies
...

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 Jul 20, 2026
@github-actions
github-actions Bot merged commit 4973f7f into main Jul 20, 2026
2 checks passed
@dependabot
dependabot Bot deleted the dependabot/go_modules/ssh-reader/go-dependencies-47fbb9ae02 branch July 20, 2026 09:07
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