Skip to content

v1.3

v1.3 #422

Triggered via pull request March 24, 2026 17:06
@johnklipijohnklipi
synchronize #139
dev1.3
Status Failure
Total duration 37s
Artifacts –

cicd.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 1 warning
CI/CD
Process completed with exit code 1.
CI/CD: src/Managers/Multiplayer.cs#L248
Dereference of a possibly null reference.
CI/CD: src/ViewModels/SetupGameDataViewModel.cs#L9
Non-nullable property 'gameSettingsJson' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
CI/CD: src/ViewModels/SetupGameDataViewModel.cs#L7
Non-nullable property 'serializedGameState' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
CI/CD: src/ViewModels/SetupGameDataViewModel.cs#L5
Non-nullable property 'lobbyId' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
CI/CD: src/Managers/Multiplayer.cs#L248
Dereference of a possibly null reference.
CI/CD: src/ViewModels/SetupGameDataViewModel.cs#L9
Non-nullable property 'gameSettingsJson' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
CI/CD: src/ViewModels/SetupGameDataViewModel.cs#L7
Non-nullable property 'serializedGameState' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
CI/CD: src/ViewModels/SetupGameDataViewModel.cs#L5
Non-nullable property 'lobbyId' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
CI/CD
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/