Skip to content

Add support for building Texworks on Windows ARM64 #487

Add support for building Texworks on Windows ARM64

Add support for building Texworks on Windows ARM64 #487

Re-run triggered April 6, 2026 18:40
Status Success
Total duration 1h 6m 10s
Artifacts 10

cd.yml

on: pull_request
Ubuntu (Launchpad)
0s
Ubuntu (Launchpad)
Linux/AppImage
14m 6s
Linux/AppImage
Windows (MSVC ARM64)
25m 45s
Windows (MSVC ARM64)
Matrix: Mac OS X
Matrix: Windows
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Mac OS X (10.13-x86)
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-python@v5, actions/upload-artifact@v4, jurplel/install-qt-action/action@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/
Mac OS X (11-x86)
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-python@v5, actions/upload-artifact@v4, jurplel/install-qt-action/action@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/
Linux/AppImage
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/upload-artifact@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/
Mac OS X (11-arm)
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-python@v5, actions/upload-artifact@v4, jurplel/install-qt-action/action@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/
Windows (MSVC ARM64)
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-python@v5, actions/upload-artifact@v4, jurplel/install-qt-action/action@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/
Windows (10)
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/upload-artifact@v4, Vampire/setup-wsl@v5. 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/
Windows (7)
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/upload-artifact@v4, Vampire/setup-wsl@v5. 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
TeXworks-AppImage
37.8 MB
sha256:5191a0a8cf997df87445f8d6c8e0e2549f85576cb3c1df95b37fbeedb5e94503
TeXworks-Windows10
28.3 MB
sha256:4102173273f09fa6c525f08c857c50439a507f8558523e992d22836549b86329
TeXworks-Windows10-Setup
27.7 MB
sha256:183a5b63ea6eb63073f2b4139218592ae0188671ea0271193f893f17c2d5a3b2
TeXworks-Windows7
26.7 MB
sha256:7072f93c73d0a46b54669b8417efd89093cb17066cd32650fd4b6744c3407b4d
TeXworks-Windows7-Setup
26.6 MB
sha256:6e3a290d3dae3c9190ed3c8bd3875d3730ea6b72cbcc426f407abce160a1ae83
TeXworks-WindowsARM64
8.42 MB
sha256:00687c93bee3a1201fca210849647bfa9ac4d340eb86bd6254787f9fa3d56409
TeXworks-WindowsARM64-Setup
17.9 MB
sha256:f533dcbe04c72907d56dade002a5fa115c7b4ed5ce6620c55d2d9870fd7251b8
TeXworks-macOS10.13-x86_64
26.4 MB
sha256:e47845488599cfea194c2f66c0404de0d4f91c32203af12955c79469cd4a6050
TeXworks-macOS11-arm64
37.6 MB
sha256:333411227c0f24d1368cd974e39589b7d1abe35ec5bd90cd4429c0e336f8d6be
TeXworks-macOS11-x86_64
37.6 MB
sha256:1c348f96c261fcbc05ed10d377997a9b157e7cce177c047fc74a8d87df60286f