Skip to content

fix: Dotnet windows init container #6

fix: Dotnet windows init container

fix: Dotnet windows init container #6

Triggered via pull request October 30, 2024 20:20
Status Success
Total duration 3m 17s
Artifacts
Read Version
3s
Read Version
Matrix: Build and Publish Containers
Publish Manifest
13s
Publish Manifest
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Read Version
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and Publish Containers (windows-2019)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and Publish Containers (windows-2022)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Publish Manifest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/