From 3fc09af6fa1c06486a334fda0f119182cc885764 Mon Sep 17 00:00:00 2001 From: GitHub Date: Mon, 7 Sep 2026 06:52:14 +0000 Subject: [PATCH 1/6] chore: update dependencies/Sentry.properties to 6.10.0 --- CHANGELOG.md | 6 +++--- dependencies/Sentry.properties | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index dd7acc2..23ba5ca 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -20,9 +20,9 @@ ### 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 diff --git a/dependencies/Sentry.properties b/dependencies/Sentry.properties index c1d5165..67dd21e 100644 --- a/dependencies/Sentry.properties +++ b/dependencies/Sentry.properties @@ -1,3 +1,3 @@ -version = 6.5.0 +version = 6.10.0 repo = https://github.com/getsentry/sentry-dotnet license = MIT From 4785f722128bc7e0e831f2a39357e9d8a44f0b6f Mon Sep 17 00:00:00 2001 From: Ivan Dlugos Date: Mon, 7 Sep 2026 09:08:35 +0200 Subject: [PATCH 2/6] docs: Drop the Logs opt-in from the send-logs sample sentry-dotnet 6.10.0 removed the EnableLogs gate on SentrySdk.Logger, which is what Write-SentryLog calls. Setting $_.EnableLogs = $true no longer has any bearing on whether Write-SentryLog emits, so the sample's "opt in to Logs" guidance now teaches something untrue. Verified against the bundled 6.10.0 assembly: a log envelope item reaches the transport with EnableLogs both set and unset, where 6.5.0 emitted only when it was set. No test covers the disabled path, which is why the change was invisible to CI. Co-Authored-By: Claude Opus 5 --- CHANGELOG.md | 1 + samples/send-logs.ps1 | 3 +-- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 23ba5ca..145f2e1 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -12,6 +12,7 @@ - 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)) +- `Write-SentryLog` no longer requires an explicit opt-in: logs are sent without setting `$_.EnableLogs = $true`. The option remains available but no longer gates `Write-SentryLog` ([#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 diff --git a/samples/send-logs.ps1 b/samples/send-logs.ps1 index 05af45a..13650a7 100644 --- a/samples/send-logs.ps1 +++ b/samples/send-logs.ps1 @@ -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. Logs are sent by default, so Write-SentryLog needs no opt-in. Start-Sentry { $_.Dsn = 'https://997874440feaba4ecc65c1e25df7912b@o447951.ingest.us.sentry.io/4508073336176640' $_.Debug = $true - $_.EnableLogs = $true } try { From ade5ca3b358188396e6469adf31c37a31c81512d Mon Sep 17 00:00:00 2001 From: Ivan Dlugos <6349682+vaind@users.noreply.github.com> Date: Mon, 7 Sep 2026 09:11:00 +0200 Subject: [PATCH 3/6] Configure Sentry client with DSN and debug mode --- samples/send-logs.ps1 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/samples/send-logs.ps1 b/samples/send-logs.ps1 index 13650a7..faeacd0 100644 --- a/samples/send-logs.ps1 +++ b/samples/send-logs.ps1 @@ -14,7 +14,7 @@ # 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. Logs are sent by default, so Write-SentryLog needs no opt-in. +# Start the Sentry client. Start-Sentry { $_.Dsn = 'https://997874440feaba4ecc65c1e25df7912b@o447951.ingest.us.sentry.io/4508073336176640' $_.Debug = $true From 08708198dc053cea7ead09d2fddca4ebd81fbca9 Mon Sep 17 00:00:00 2001 From: Ivan Dlugos Date: Mon, 7 Sep 2026 09:15:18 +0200 Subject: [PATCH 4/6] docs: Fold the Logs opt-in note into the Write-SentryLog entry Write-SentryLog and the SDK bump that removed the EnableLogs gate both land in the same unreleased cycle, so describing the removal as its own entry documents a change no released version ever exposed. Readers of the next release only need to know the cmdlet exists, so reference #137 from the entry that introduced it instead. Drop the EnableLogs half of the breaking-changes entry for the same reason: it directed readers to set $_.EnableLogs, which is no longer required for Write-SentryLog to emit. Co-Authored-By: Claude Opus 5 --- CHANGELOG.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 145f2e1..8470dde 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,13 +11,12 @@ - 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)) -- `Write-SentryLog` no longer requires an explicit opt-in: logs are sent without setting `$_.EnableLogs = $true`. The option remains available but no longer gates `Write-SentryLog` ([#137](https://github.com/getsentry/sentry-powershell/pull/137)) +- Add `Write-SentryLog` cmdlet, a native PowerShell API for sending structured logs (Sentry Logs) ([#131](https://github.com/getsentry/sentry-powershell/pull/131), [#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)) +- Sentry Logs (`Write-SentryLog`) options have moved off `Experimental`: use `$_.SetBeforeSendLog(...)` instead of `$_.Experimental.SetBeforeSendLog(...)` ([#133](https://github.com/getsentry/sentry-powershell/pull/133)) ### Dependencies From 3df2afdb4f88b3914da796c852884e05177b00a7 Mon Sep 17 00:00:00 2001 From: Ivan Dlugos Date: Mon, 7 Sep 2026 09:21:52 +0200 Subject: [PATCH 5/6] docs: Drop the Experimental breaking-change entry Write-SentryLog (#131) and the move of its options off Experimental (#133) both land in this same unreleased cycle, so no released version ever exposed $_.Experimental.SetBeforeSendLog through the module. There is nothing for a user upgrading from 0.4.0 to migrate. Reaching past the module into the bundled SDK's options object was the only way to touch it from 0.4.0, and the Dependencies entry for the 5.16.1 -> 6.10.0 bump already covers that surface. Co-Authored-By: Claude Opus 5 --- CHANGELOG.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 8470dde..dd0b77e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -14,10 +14,6 @@ - Add `Write-SentryLog` cmdlet, a native PowerShell API for sending structured logs (Sentry Logs) ([#131](https://github.com/getsentry/sentry-powershell/pull/131), [#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 `$_.SetBeforeSendLog(...)` instead of `$_.Experimental.SetBeforeSendLog(...)` ([#133](https://github.com/getsentry/sentry-powershell/pull/133)) - ### Dependencies - 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)) From 4def6643d90d4d1cc92f045b9b46b2e2bddf0796 Mon Sep 17 00:00:00 2001 From: Ivan Dlugos Date: Mon, 7 Sep 2026 09:24:14 +0200 Subject: [PATCH 6/6] docs: Credit #133 on the Write-SentryLog entry #133 moved the Logs options off Experimental and updated the sample and tests accordingly, so it shaped the logging surface users see. Its attribution lived in the breaking-change entry that was just removed; fold it into the feature entry rather than losing it. Co-Authored-By: Claude Opus 5 --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index dd0b77e..3a9a4f3 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,7 +11,7 @@ - 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), [#137](https://github.com/getsentry/sentry-powershell/pull/137)) +- 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)) ### Dependencies