Skip to content

fix(ci): Update validate-pr action to remove draft enforcement #13363

fix(ci): Update validate-pr action to remove draft enforcement

fix(ci): Update validate-pr action to remove draft enforcement #13363

Triggered via pull request March 30, 2026 09:48
Status Success
Total duration 54m 51s
Artifacts 9

build.yml

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

Annotations

2 errors and 15 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.2
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. Node.js 20 will be removed from the runner on September 16th, 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. Node.js 20 will be removed from the runner on September 16th, 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. Node.js 20 will be removed from the runner on September 16th, 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 (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. Node.js 20 will be removed from the runner on September 16th, 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-arm64)
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. Node.js 20 will be removed from the runner on September 16th, 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. Node.js 20 will be removed from the runner on September 16th, 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. Node.js 20 will be removed from the runner on September 16th, 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): src/Sentry.Bindings.Cocoa/ApiDefinitions.cs#L1755
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
.NET (macos): src/Sentry.Bindings.Cocoa/ApiDefinitions.cs#L1755
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
.NET (macos): src/Sentry.Bindings.Cocoa/ApiDefinitions.cs#L1755
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
.NET (macos): src/Sentry.Bindings.Cocoa/ApiDefinitions.cs#L1755
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
.NET (macos)
Already linked: /opt/homebrew/Cellar/mono/6.14.1
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. Node.js 20 will be removed from the runner on September 16th, 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 (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. Node.js 20 will be removed from the runner on September 16th, 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
17b7ee92914fc120af9a52413dbe80ffb1115697
166 MB
sha256:a6fdc1dba5a0e9392213e35f7db2292df29f4ac0d1a8ac984048c993f75dd97c
Windows-msbuild-logs
118 MB
sha256:a5fa1366616444d822a796f89caf90178d7bb2f5f29596eaebf6ae347a50a17c
linux-arm64-build-logs
50.4 MB
sha256:c4fb22d73a02dd29725fdf3b8e7af4d1bddae50fc4c1364026c843f7bf62b644
linux-musl-arm64-build-logs
50.1 MB
sha256:c9e915ed38838775fd011485a06dca0cb4930d04c41847629f525b44135eb7fa
linux-musl-x64-build-logs
50.2 MB
sha256:4798554f12d9560417f756d5c524d27d99c560a3457ba8cebc9a33a33056ec90
linux-x64-build-logs
83.4 MB
sha256:6410c91f07ebd468b49ae9fb316c29b32a095db02859b376b944d2efe8c0b375
macos-build-logs
117 MB
sha256:7d5d9e028d1431756ef545744c3d200783f55d5891c3b5ab37b96e64f41e6855
win-arm64-build-logs
73.9 MB
sha256:ba97d1a09c8cc624274db658eb52b29d8f153b49e144206472896ba686f40201
win-x64-build-logs
79.1 MB
sha256:93874060f2bdbd87c4ba921b1ee9efdbb57a6de5d9e3fbe85c066e904fec1ac1