Skip to content

feat: User.Id can now be overriden (set to null) in Global mode #13280

feat: User.Id can now be overriden (set to null) in Global mode

feat: User.Id can now be overriden (set to null) in Global mode #13280

Triggered via pull request March 23, 2026 07:16
Status Success
Total duration 1h 0m 31s
Artifacts 9

build.yml

on: pull_request
Matrix: build-sentry-native
test-solution-filters
36s
test-solution-filters
Matrix: build-sentry
Matrix: unsupported-aot
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 20 warnings
.NET (linux-x64)
You may need to build the project on another operating system or architecture, or update the .NET SDK.
.NET (linux-x64)
The project depends on the following workload packs that do not exist in any of the workloads available in this installation: Microsoft.iOS.Sdk.net9.0_26.0
Trim analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Trim analysis
Already linked: /opt/homebrew/Cellar/mono/6.14.1
.NET (linux-arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MSBuild
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f, microsoft/setup-msbuild@6fb02220983dee41ce7ae257b6f4d8f9bf5ed4ce. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
.NET (linux-x64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
.NET (win-x64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
.NET (macos)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
.NET (macos)
Already linked: /opt/homebrew/Cellar/mono/6.14.1
Unsupported AOT (linux-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Unsupported AOT (win-x86)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
Windows-msbuild-logs
95.8 MB
sha256:d2ba028f51571d52c630aabdd9ea1be91d51595712d3bf90134c0cdc9c4d7798
fa9f1ad59023fa04b9524a7aab8a073753b28101
165 MB
sha256:0380b35ac5fb8d1d133cbc897274d58db5d450b96025c713e24591ba4789c67d
linux-arm64-build-logs
50.4 MB
sha256:c0855d6b629b83bdebc962e65c768c68809f17819373222946239e578176501f
linux-musl-arm64-build-logs
50.2 MB
sha256:a7a24d02bb6bd1f5878e6ba841212a4d7c4f16e774d419c30b1a2f411e28c27b
linux-musl-x64-build-logs
50.2 MB
sha256:5104170f13ae5f174a5ddbbe85754d77542357ec015a2d63d4a0dec12fb64624
linux-x64-build-logs
83.2 MB
sha256:ff20dcf5b73db8d3bf664177bf47c0babd9a0d10b85dfe4657fe1acfd33602da
macos-build-logs
117 MB
sha256:856a6be5dc02e05bc46b5da2db1a5527442b69a1967d69716c4fcfd8896aa0ae
win-arm64-build-logs
73.2 MB
sha256:4ee9b05f8a284f38c4eeffe5cab954175662586e0dbbbddcb60bef2c33e86485
win-x64-build-logs
78.5 MB
sha256:00d2b650a007e73a0fc034223c81363e0749d9646f0ef87618cff04cefc31e5f