Skip to content

OSOE-1208: Use our own MSBuild SDKs #229

OSOE-1208: Use our own MSBuild SDKs

OSOE-1208: Use our own MSBuild SDKs #229

Triggered via pull request April 7, 2026 11:09
Status Success
Total duration 1m 56s
Artifacts 1

validate-nuget-publish.yml

on: pull_request
Validate NuGet Publish  /  ...  /  Publish to NuGet
1m 51s
Validate NuGet Publish / Validate NuGet Publish / Publish to NuGet
Fit to window
Zoom out
Zoom in

Annotations

3 warnings and 1 notice
Validate NuGet Publish / Validate NuGet Publish / Publish to NuGet
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildsville/add-remove-label@ac59c9f0aeb66eb12d6366eb1d69ec1906e9ef9a. 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/
Validate NuGet Publish / Validate NuGet Publish / Publish to NuGet
Package version couldn't be added, thus package validation to the baseline version won't be done.
Validate NuGet Publish / Validate NuGet Publish / Publish to NuGet
Package version couldn't be added, thus package validation to the baseline version won't be done.
Validate NuGet Publish / Validate NuGet Publish / Publish to NuGet
Dry run mode: Package created successfully but will not be published.

Artifacts

Produced during runtime
Name Size Digest
NuGet-Package Expired
2.44 MB
sha256:c187bb3efb99ec5f29e1fa9299ed2513e25baf8c7eea0312bbebd33085ec03f9