Skip to content

feat: migrate from Wails v2 to v3 #17

feat: migrate from Wails v2 to v3

feat: migrate from Wails v2 to v3 #17

Triggered via pull request March 21, 2026 01:48
Status Cancelled
Total duration 4m 43s
Artifacts

pr.yml

on: pull_request
Matrix: build-artifacts
Fit to window
Zoom out
Zoom in

Annotations

19 errors and 5 warnings
e2e-tests
Canceling since a higher priority waiting request for pr-44 exists
e2e-tests
cannot use b (variable of type *BrowserWindow) as Window value in return statement: *BrowserWindow does not implement Window (missing method AttachModal)
e2e-tests
cannot use b (variable of type *BrowserWindow) as Window value in return statement: *BrowserWindow does not implement Window (missing method AttachModal)
e2e-tests
cannot use b (variable of type *BrowserWindow) as Window value in return statement: *BrowserWindow does not implement Window (missing method AttachModal)
e2e-tests
cannot use b (variable of type *BrowserWindow) as Window value in return statement: *BrowserWindow does not implement Window (missing method AttachModal)
e2e-tests
cannot use b (variable of type *BrowserWindow) as Window value in return statement: *BrowserWindow does not implement Window (missing method AttachModal)
e2e-tests
cannot use b (variable of type *BrowserWindow) as Window value in return statement: *BrowserWindow does not implement Window (missing method AttachModal)
e2e-tests
cannot use b (variable of type *BrowserWindow) as Window value in return statement: *BrowserWindow does not implement Window (missing method AttachModal)
e2e-tests
cannot use b (variable of type *BrowserWindow) as Window value in return statement: *BrowserWindow does not implement Window (missing method AttachModal)
e2e-tests
cannot use b (variable of type *BrowserWindow) as Window value in return statement: *BrowserWindow does not implement Window (missing method AttachModal)
e2e-tests
cannot use b (variable of type *BrowserWindow) as Window value in return statement: *BrowserWindow does not implement Window (missing method AttachModal)
build-artifacts (ubuntu-latest, linux/amd64, pr-build-linux, production,webkit2_41)
Canceling since a higher priority waiting request for pr-44 exists
build-artifacts (windows-latest, windows/amd64, pr-build-windows, production, -H windowsgui)
Canceling since a higher priority waiting request for pr-44 exists
Task 'packages' failed
exit status 58
build-artifacts (macos-latest, darwin/universal, pr-build-macos, production)
Canceling since a higher priority waiting request for pr-44 exists
PR Validation
Canceling since a higher priority waiting request for pr-44 exists
e2e-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/setup-go@v5, actions/setup-node@v4, actions/upload-artifact@v4, arduino/setup-task@v2. 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/
e2e-tests
No files were found with the provided path: e2e/playwright-report/ e2e/test-results/. No artifacts will be uploaded.
build-artifacts (ubuntu-latest, linux/amd64, pr-build-linux, production,webkit2_41)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/setup-go@v5, actions/setup-node@v4, arduino/setup-task@v2. 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/
build-artifacts (windows-latest, windows/amd64, pr-build-windows, production, -H windowsgui)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5, actions/setup-node@v4, arduino/setup-task@v2. 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/
build-artifacts (macos-latest, darwin/universal, pr-build-macos, production)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5, actions/setup-node@v4, arduino/setup-task@v2. 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/