Skip to content

chore(deps): update Dotnet SDK to v6.10.0 #137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vaind merged 6 commits into from
Sep 7, 2026
+6 −11
Merged

chore(deps): update Dotnet SDK to v6.10.0 #137

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
3fc09af
chore: update dependencies/Sentry.properties to 6.10.0
web-flow Sep 7, 2026
4785f72
docs: Drop the Logs opt-in from the send-logs sample
vaind Sep 7, 2026
ade5ca3
Configure Sentry client with DSN and debug mode
vaind Sep 7, 2026
0870819
docs: Fold the Logs opt-in note into the Write-SentryLog entry
vaind Sep 7, 2026
3df2afd
docs: Drop the Experimental breaking-change entry
vaind Sep 7, 2026
4def664
docs: Credit #133 on the Write-SentryLog entry
vaind Sep 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 4 additions & 8 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,18 +11,14 @@
- Honor `InAppInclude` / `InAppExclude` options when classifying PowerShell stack frames. Entries are matched against the PowerShell module name (the directory under a `$env:PSModulePath` entry) with prefix-then-dot semantics, mirroring how the .NET SDK matches namespaces. Regex variants (`AddInAppIncludeRegex` / `AddInAppExcludeRegex`) are also supported. The existing default — module frames are not in-app, script frames are — is preserved for modules not matched by any rule. ([#135](https://github.com/getsentry/sentry-powershell/pull/135))
- Add `Add-SentryAttachment` cmdlet that infers a content type from the file extension (including PowerShell-specific extensions like `.ps1`, `.psm1`, `.psd1`) so the Sentry UI can preview attachments as text/JSON instead of falling back to `application/octet-stream` ([#134](https://github.com/getsentry/sentry-powershell/pull/134))
- Add support for .NET 10 / PowerShell 7.6 ([#133](https://github.com/getsentry/sentry-powershell/pull/133))
- Add `Write-SentryLog` cmdlet, a native PowerShell API for sending structured logs (Sentry Logs) ([#131](https://github.com/getsentry/sentry-powershell/pull/131))
- Add `Write-SentryLog` cmdlet, a native PowerShell API for sending structured logs (Sentry Logs) ([#131](https://github.com/getsentry/sentry-powershell/pull/131), [#133](https://github.com/getsentry/sentry-powershell/pull/133), [#137](https://github.com/getsentry/sentry-powershell/pull/137))
- Add `Add-SentryEventProcessor` cmdlet for registering a global event processor from a PowerShell script block ([#130](https://github.com/getsentry/sentry-powershell/pull/130))

### Breaking changes

- Sentry Logs (`Write-SentryLog`) options have moved off `Experimental`: use `$_.EnableLogs` and `$_.SetBeforeSendLog(...)` instead of `$_.Experimental.EnableLogs` / `$_.Experimental.SetBeforeSendLog(...)` ([#133](https://github.com/getsentry/sentry-powershell/pull/133))

### Dependencies

- Bump Dotnet SDK from v5.16.1 to v6.5.0 ([#133](https://github.com/getsentry/sentry-powershell/pull/133))
- [changelog](https://github.com/getsentry/sentry-dotnet/blob/main/CHANGELOG.md#650)
- [diff](https://github.com/getsentry/sentry-dotnet/compare/5.16.1...6.5.0)
- Bump Dotnet SDK from v5.16.1 to v6.10.0 ([#133](https://github.com/getsentry/sentry-powershell/pull/133), [#137](https://github.com/getsentry/sentry-powershell/pull/137))
- [changelog](https://github.com/getsentry/sentry-dotnet/blob/main/CHANGELOG.md#6100)
- [diff](https://github.com/getsentry/sentry-dotnet/compare/5.16.1...6.10.0)

## 0.4.0

Expand Down
2 changes: 1 addition & 1 deletion dependencies/Sentry.properties
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
version = 6.5.0
version = 6.10.0
repo = https://github.com/getsentry/sentry-dotnet

@sentry sentry Bot Jul 27, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The dependency upgrade to Sentry .NET SDK v6.8.0 may break reflection-based access to internal APIs like HttpTransportBase.ProcessEnvelope, causing initialization failures.
Severity: HIGH

Suggested Fix

Verify that the internal Sentry .NET SDK APIs accessed via reflection still exist and have the same signatures in v6.8.0. If they have changed, update the reflection code in SynchronousTransport.ps1 and New-HttpTransport.ps1 to match the new API. Consider adding tests that validate the reflection against the new SDK version to prevent future breakages.

Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: dependencies/Sentry.properties#L2

Potential issue: The `sentry-powershell` module uses reflection to access internal,
non-public APIs of the Sentry .NET SDK, including `HttpTransportBase.ProcessEnvelope`,
`HttpTransportBase.CreateRequest`, and `SdkComposer.CreateHttpTransport()`. This pull
request upgrades the SDK from v6.5.0 to v6.8.0. There is a risk that these internal
APIs, which are not part of the public contract, have changed between versions. If they
have, the reflection calls will fail during `Start-Sentry` initialization, throwing an
exception. This will be logged as a warning and may either cause the script to fail or
continue without the custom synchronous transport, depending on the
`SentryPowershellRethrowErrors` global flag.

Did we get this right? 👍 / 👎 to inform future reviews.

license = MIT
3 changes: 1 addition & 2 deletions samples/send-logs.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,11 +14,10 @@
# Import the Sentry module. In your code, you would just use `Import-Module Sentry`.
Import-Module $PSScriptRoot/../modules/Sentry/Sentry.psd1

# Start the Sentry client. Set EnableLogs = $true to opt in to Logs.
# Start the Sentry client.
Start-Sentry {
$_.Dsn = 'https://[email protected]/4508073336176640'
$_.Debug = $true
$_.EnableLogs = $true
}

try {
Expand Down
Loading