Skip to content
Build Managed

Updated UnitTests to use the same strongnaming logic as the main SDK #124

Sign in to view logs

Updated UnitTests to use the same strongnaming logic as the main SDK

Updated UnitTests to use the same strongnaming logic as the main SDK #124

Triggered via pull request August 27, 2024 18:22
@jstedfastjstedfast
synchronize #178
dev/jestedfa/github-pipeline-fix2
Status Failure
Total duration 1m 49s
Artifacts –

main.yml

on: pull_request
managed-build
1m 27s
managed-build
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
managed-build
Process completed with exit code 1.
managed-build
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
managed-build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v2, microsoft/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
managed-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/