Merge branch 'feature/http_id_retriever' into develop #11
Annotations
10 warnings
build-and-push
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-dotnet@v2, docker/setup-qemu-action@v2, docker/setup-buildx-action@v2, docker/build-push-action@v4. 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-push
One of '--self-contained' or '--no-self-contained' options are required when '--runtime' is used.
|
build-and-push:
castledice-matchmaker/Configuration/AuthBackendConnectionOptions.cs#L5
Non-nullable property 'Url' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
build-and-push:
castledice-matchmaker/MessageHandlers/RequestGameMessageHandler.cs#L9
Non-nullable field '_dtoAccepter' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
build-and-push:
castledice-matchmaker/MessageHandlers/CancelGameMessageHandler.cs#L9
Non-nullable field '_dtoAccepter' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
build-and-push
One of '--self-contained' or '--no-self-contained' options are required when '--runtime' is used.
|
build-and-push:
castledice-matchmaker/Configuration/AuthBackendConnectionOptions.cs#L5
Non-nullable property 'Url' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
build-and-push:
castledice-matchmaker/MessageHandlers/RequestGameMessageHandler.cs#L9
Non-nullable field '_dtoAccepter' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
build-and-push:
castledice-matchmaker/MessageHandlers/CancelGameMessageHandler.cs#L9
Non-nullable field '_dtoAccepter' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
build-and-push
.NET 7.0 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.
|