SteamKit2 Continuous Integration #119
Annotations
16 errors and 16 warnings
.NET on ubuntu-latest (Debug):
DepotDownloader/Steam3Session.cs#L752
The type name 'UpdateMachineAuthCallback' does not exist in the type 'SteamUser'
|
.NET on ubuntu-latest (Debug)
Process completed with exit code 1.
|
.NET on ubuntu-latest (Release):
DepotDownloader/Steam3Session.cs#L752
The type name 'UpdateMachineAuthCallback' does not exist in the type 'SteamUser'
|
.NET on ubuntu-latest (Release)
Process completed with exit code 1.
|
.NET on windows-latest (Release):
DepotDownloader/Steam3Session.cs#L752
The type name 'UpdateMachineAuthCallback' does not exist in the type 'SteamUser'
|
.NET on windows-latest (Release)
Process completed with exit code 1.
|
.NET on windows-latest (Debug):
DepotDownloader/Steam3Session.cs#L752
The type name 'UpdateMachineAuthCallback' does not exist in the type 'SteamUser'
|
.NET on windows-latest (Debug)
Process completed with exit code 1.
|
.NET on macos-14 (Release):
DepotDownloader/Steam3Session.cs#L752
The type name 'UpdateMachineAuthCallback' does not exist in the type 'SteamUser'
|
.NET on macos-14 (Release)
Process completed with exit code 1.
|
.NET on macos-14 (Debug):
DepotDownloader/Steam3Session.cs#L752
The type name 'UpdateMachineAuthCallback' does not exist in the type 'SteamUser'
|
.NET on macos-14 (Debug)
Process completed with exit code 1.
|
.NET on macos-latest (Debug):
DepotDownloader/Steam3Session.cs#L752
The type name 'UpdateMachineAuthCallback' does not exist in the type 'SteamUser'
|
.NET on macos-latest (Debug)
Process completed with exit code 1.
|
.NET on macos-latest (Release):
DepotDownloader/Steam3Session.cs#L752
The type name 'UpdateMachineAuthCallback' does not exist in the type 'SteamUser'
|
.NET on macos-latest (Release)
Process completed with exit code 1.
|
.NET on ubuntu-latest (Debug)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
.NET on ubuntu-latest (Debug)
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.
|
.NET on ubuntu-latest (Release)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
.NET on ubuntu-latest (Release)
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.
|
.NET on windows-latest (Release)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
.NET on windows-latest (Release)
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.
|
.NET on windows-latest (Debug)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
.NET on windows-latest (Debug)
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.
|
.NET on macos-14 (Release)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
.NET on macos-14 (Release)
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.
|
.NET on macos-14 (Debug)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
.NET on macos-14 (Debug)
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.
|
.NET on macos-latest (Debug)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
.NET on macos-latest (Debug)
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.
|
.NET on macos-latest (Release)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
.NET on macos-latest (Release)
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.
|