Skip to content

fix: sync csproj assembly version to 0.5.4-alpha #62

fix: sync csproj assembly version to 0.5.4-alpha

fix: sync csproj assembly version to 0.5.4-alpha #62

Triggered via push April 7, 2026 01:16
Status Success
Total duration 4m 43s
Artifacts 2

build.yml

on: push
Publish Release Exe
3m 0s
Publish Release Exe
Build Inno Setup Installer
0s
Build Inno Setup Installer
Update Rolling Alpha Release
28s
Update Rolling Alpha Release
Create GitHub Release
Create GitHub Release
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
Build & Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Build & Test: src/PortPane/ViewModels/MainViewModel.cs#L162
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build & Test: src/PortPane/ViewModels/MainViewModel.cs#L162
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build & Test: src/PortPane/ViewModels/MainViewModel.cs#L162
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build & Test: src/PortPane/ViewModels/MainViewModel.cs#L162
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Publish Release Exe
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Publish Release Exe: src/PortPane/ViewModels/MainViewModel.cs#L162
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Publish Release Exe: src/PortPane/ViewModels/MainViewModel.cs#L162
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Update Rolling Alpha Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: softprops/action-gh-release@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Artifacts

Produced during runtime
Name Size Digest
PortPane-0.5.4-alpha.20260407-0118-a867e5ae9c4babed1f60e7c186ded98788514ac6
89.8 MB
sha256:4436368a28338f5e48066cfcaeb7b034b8c4e1a8fcc20e9679b75ac6d8ef0d09
test-results-a867e5ae9c4babed1f60e7c186ded98788514ac6
14.3 KB
sha256:b6aee465f9a660a2dd906f3a995fad2bfe659c16482b7205e54c9b0886cf66eb