Skip to content

build(deps): bump github.com/getsentry/sentry-go from 0.47.0 to 0.48.0 - #350

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/github.com/getsentry/sentry-go-0.48.0
Open

build(deps): bump github.com/getsentry/sentry-go from 0.47.0 to 0.48.0#350
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/github.com/getsentry/sentry-go-0.48.0

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps 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

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Jul 16, 2026
@mendral-app

mendral-app Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

🔍 PR Interaction Analysis

This PR is a dependency version bump (github.com/getsentry/sentry-go v0.47.0 → v0.48.0), affecting only go.mod and go.sum.

No application logic, control flow, or component interactions are changed — only the pinned version of an external dependency is updated. A sequence diagram is not applicable here.

Summary: Routine dependency update managed by Dependabot. No new inter-component interactions introduced.

Note

Posted by PR Sequence Diagram · Tag @mendral-app with feedback.

@mendral-app

mendral-app Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

🧪 Testing Guide

What this PR addresses

This is an automated dependency bump of github.com/getsentry/sentry-go from v0.47.0 to v0.48.0. The upstream release includes a breaking change: removal of issue creation from logging integrations.

Steps to verify

Since this is a dependency version bump with a noted breaking change (removal of issue creation from logging integrations), reviewers should:

  1. Confirm the project builds successfully:
    go build ./...
    
  2. Run the full test suite:
    go test ./...
    
  3. Check if this codebase uses Sentry's logging integrations (e.g., sentrylogrus, sentryzap, sentryzerolog) that previously created issues from log entries. If so, verify that the removal of that behavior is acceptable or that the code has been adapted.

What to verify (expected behavior)

  • Build passes with no compilation errors related to the sentry-go API.
  • All tests pass without regressions.
  • No runtime impact — if this project relies on Sentry logging integrations to create issues, confirm that the changed behavior (logs no longer auto-creating Sentry issues) is intentional and acceptable for your use case. If issue creation from logs is needed, an alternative approach may be required.

Note

Posted by PR Testing Guide · Tag @mendral-app with feedback.

mendral-app[bot]

This comment was marked as outdated.

@mendral-app

mendral-app Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

📋 Created Linear issue ENG-3970 — status: In Progress

  • Assignee: None (bot PR — no human reviewer found)
  • Labels: Improvement
  • Estimate: XS (2 files, 6 lines changed)
  • PR linked: ✅ Issue will auto-close when this PR merges

Auto-created because no Linear reference was found in the PR title, description, or branch name.

Note

Posted by Linear Issue Enforcer · Tag @mendral-app with feedback.

Bumps [github.com/getsentry/sentry-go](https://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)

---
updated-dependencies:
- dependency-name: github.com/getsentry/sentry-go
  dependency-version: 0.48.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/getsentry/sentry-go-0.48.0 branch from 2c8108c to ec31a47 Compare July 30, 2026 21:52
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