Skip to content

✂️ v0.0.3

✂️ v0.0.3 #10

Triggered via release July 16, 2024 17:44
@isadorasophiaisadorasophia
published v0.0.3
Status Success
Total duration 2m 29s
Artifacts

ci.yaml

on: release
📦 Pack and publish
23s
📦 Pack and publish
Matrix: 📪 Release
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
📦 Pack and publish
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-dotnet@v1, NuGet/setup-nuget@v1.0.5. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
📦 Pack and publish
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-dotnet@v1, NuGet/setup-nuget@v1.0.5. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
📦 Pack and publish
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/
📪 Release (linux)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
📪 Release (linux)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-dotnet@v1, softprops/action-gh-release@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
📪 Release (linux)
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
📪 Release (macOS)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
📪 Release (macOS)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-dotnet@v1, softprops/action-gh-release@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
📪 Release (macOS)
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
📪 Release (windows)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
📪 Release (windows)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-dotnet@v1, softprops/action-gh-release@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
📪 Release (windows)
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.