Skip to content

Zen Release builds #942

Zen Release builds

Zen Release builds #942

Manually triggered March 26, 2026 15:56
Status Success
Total duration 17h 41m 23s
Artifacts 23

build.yml

on: workflow_dispatch
Generate build ID
7s
Generate build ID
start-self-host
3m 1s
start-self-host
Generate build data
32s
Generate build data
Matrix: Linux build / build-linux
check-release
21s
check-release
Matrix: macOS build / mac-build
Matrix: Windows build step 1 (PGO build) / windows-build
Matrix: appimage
macOS build (Universal)  /  Unify macOS (Universal)
31m 37s
macOS build (Universal) / Unify macOS (Universal)
Matrix: Windows build step 2 (Generate profile data) / windows-profile-build
Matrix: Windows build step 3 (build with profile data) / windows-build
stop-self-hosted
18s
stop-self-hosted
Prepare Flatpak
2m 15s
Prepare Flatpak
Release Flatpak
25s
Release Flatpak
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
mr-cheffy
approved Mar 27, 2026
Deploy-Release

Annotations

33 warnings
Workflow syntax warning: .github/workflows/build.yml#L120
.github/workflows/build.yml (Line: 120, Col: 13): Conditional expression contains literal text outside replacement tokens. This will cause the expression to always evaluate to truthy. Did you mean to put the entire expression inside ${{ }}?
Workflow syntax warning: .github/workflows/build.yml#L462
.github/workflows/build.yml (Line: 462, Col: 13): Conditional expression contains literal text outside replacement tokens. This will cause the expression to always evaluate to truthy. Did you mean to put the entire expression inside ${{ }}?
Generate build ID
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 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/
Generate build data
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/setup-node@v5. 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/
check-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/setup-node@v5. 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/
Windows build step 1 (PGO build) / Build Windows - aarch64
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/github-script@v6, useblacksmith/cache@v5, useblacksmith/setup-node@v5. 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/
source
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, useblacksmith/setup-node@v5. 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/
Linux build / Build Linux - aarch64
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/github-script@v6, actions/upload-artifact@v4, useblacksmith/setup-node@v5. 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/
Windows build step 1 (PGO build) / Build Windows - x86_64
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/github-script@v6, actions/upload-artifact@v4, useblacksmith/cache@v5, useblacksmith/setup-node@v5. 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/
Windows build step 2 (Generate profile data) / Windows Profile Build - aarch64
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-node@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/
Windows build step 2 (Generate profile data) / Windows Profile Build - x86_64
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/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@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/
Windows build step 3 (build with profile data) / Build Windows - aarch64
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/github-script@v6, actions/upload-artifact@v4, useblacksmith/cache@v5, useblacksmith/setup-node@v5. 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/
macOS build / Build macOS - x86_64
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/github-script@v6, actions/setup-node@v4, actions/setup-python@v5, 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/
macOS build / Build macOS - x86_64
gnu-tar 1.35 is already installed and up-to-date. To reinstall 1.35, run: brew reinstall gnu-tar
macOS build / Build macOS - x86_64
cairo 1.18.4 is already installed and up-to-date. To reinstall 1.18.4, run: brew reinstall cairo
Linux build / Build Linux - x86_64
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/github-script@v6, actions/upload-artifact@v4, useblacksmith/setup-node@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/
Linux build / Build Linux - x86_64
The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding...
AppImage build - Linux x86_64
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/download-artifact@v4, actions/upload-artifact@v4, useblacksmith/setup-node@v5. 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/
AppImage build - Linux aarch64
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/download-artifact@v4, actions/upload-artifact@v4, useblacksmith/setup-node@v5. 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/
macOS build / Build macOS - aarch64
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/github-script@v6, actions/setup-node@v4, actions/setup-python@v5, 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/
macOS build / Build macOS - aarch64
gnu-tar 1.35 is already installed and up-to-date. To reinstall 1.35, run: brew reinstall gnu-tar
macOS build / Build macOS - aarch64
cairo 1.18.4 is already installed and up-to-date. To reinstall 1.18.4, run: brew reinstall cairo
macOS build (Universal) / Unify macOS (Universal)
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/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, Apple-Actions/import-codesign-certs@v3. 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/
macOS build (Universal) / Unify macOS (Universal)
gnu-tar 1.35 is already installed and up-to-date. To reinstall 1.35, run: brew reinstall gnu-tar
macOS build (Universal) / Unify macOS (Universal)
cairo 1.18.4 is already installed and up-to-date. To reinstall 1.18.4, run: brew reinstall cairo
Windows build step 3 (build with profile data) / Build Windows - x86_64
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/download-artifact@v4, actions/github-script@v6, actions/upload-artifact@v4, useblacksmith/cache@v5, useblacksmith/setup-node@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 build step 3 (build with profile data) / Build Windows - x86_64
Failed to report failure to api.blacksmith.sh
Windows build step 3 (build with profile data) / Build Windows - x86_64
Failed to restore: Cache service responded with 401
Windows build step 3 (build with profile data) / Build Windows - x86_64
The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding...
Release
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/download-artifact@v4, softprops/action-gh-release@v2.2.2, stefanzweifel/git-auto-commit-action@v5. 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/
Prepare Flatpak
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, stefanzweifel/git-auto-commit-action@v5. 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/
Release Flatpak
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/download-artifact@v4, actions/upload-artifact@v4, peter-evans/create-pull-request@v7. 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/
Release Flatpak
Unexpected input(s) 'git-token', valid inputs are ['token', 'branch-token', 'path', 'add-paths', 'commit-message', 'committer', 'author', 'signoff', 'branch', 'delete-branch', 'branch-suffix', 'base', 'push-to-fork', 'sign-commits', 'title', 'body', 'body-path', 'labels', 'assignees', 'reviewers', 'team-reviewers', 'milestone', 'draft', 'maintainer-can-modify']

Artifacts

Produced during runtime
Name Size Digest
app.zen_browser.zen.yml
1.12 KB
sha256:a5d26785923585e9e081e18780db61ac10e0640deacee31f5802407bde47656e
linux-aarch64.mar
73.1 MB
sha256:32b8160013b745bc8357adc7dfd4d4bddfa81a51f346cec373c43e6b6c21d7b0
linux.mar
86.9 MB
sha256:1b76659d29bb7e5b01822276b393d70c6d9237aab8fe29a0b6023103aade0bdd
linux_update_manifest_aarch64
528 Bytes
sha256:514d50ddf0c24527b3ac985e5a269febda3ec333af4ad169b138f6460e098902
linux_update_manifest_x86_64
517 Bytes
sha256:0061fa0bc534f83f003e41460011951f2a152de6c886705f4446dabc1e4e2b0e
macos.mar
134 MB
sha256:dd7b88b9024444a86d30b4a6f8fe53930f68343e86b453fe55210096aed0b19c
macos_update_manifest
2.52 KB
sha256:4927e494225e6770c8d7703846041e8e1f881f8515ae34d4428949a102fc7132
platform.ini Expired
275 Bytes
sha256:4d39578cdbe5cfd472d56db53c24be9e6722f3dd70aebf9b2204bbba445f220f
windows-profdata-x86_64 Expired
35.7 MB
sha256:fec2b592b0c8b779632178c34ac0cdc5b506f6b2c95b1672a4f703376fbf5c9f
windows-x64-obj-arm64 Expired
1.68 GB
sha256:54358c51cbd4287d8477fe525500b272c758fe5dca1a0d22a6919ed247974db5
windows-x64-obj-x86_64 Expired
1.72 GB
sha256:a7541cab023cf7b9dfdbcf1a4f7490160f80f7990d74ea95ce0613e4042d276e
x86_64-zen-windows-profile-data-and-jarlog.zip
199 MB
sha256:5d10bf1d3c86d00ee60dd11e6ff180b855dad052673f16650d09d7c74ff39534
zen-aarch64-apple-darwin-dist.dmg Expired
101 MB
sha256:c0f204cfef64cfd79f36842e3721e2764b775c3de16073a55a7b44900c474aeb
zen-aarch64.AppImage
100 MB
sha256:4cd3c476cf3fc095fed4da556a525cf382a1ea5bb611857b0507e8a14570e174
zen-aarch64.AppImage.zsync
176 KB
sha256:ff2fd9a2393971b7348550d3b0d6f28bbb2165c134d4124a917a1aed3e21e69d
zen-macos-host-mar Expired
10.7 KB
sha256:95ae2f5cc7fe32b7a09ad8bfff0ec773476855ccf4b51a736c19852303352506
zen-x86_64-apple-darwin-dist.dmg Expired
107 MB
sha256:6dbca680d40771af127f4b47a1edb58d44dfc4c3f978102f4e63e9155003839d
zen-x86_64.AppImage
113 MB
sha256:499d73dabda55eb7ce101aa64a683983856cbe2023c3586049a9fe9b3140ca65
zen-x86_64.AppImage.zsync
199 KB
sha256:9e3f91ed35d59093aa2a669d1ff552e9732c43f8efde73648aed7b038eb9f286
zen.linux-aarch64.tar.xz
72.9 MB
sha256:f04c653025416d84724f596efc2088580b052d71e9bfd6b86b9e0c97f6e26e40
zen.linux-x86_64.tar.xz
84.4 MB
sha256:c76e7deb58db20b498a266121db57494123c5952416c91e81657f88449356608
zen.macos-universal.dmg
194 MB
sha256:a08a537f1251b24c05de5609ecfdafa0b9c638d7860aa5f5516c995e1beb1d57
zen.source.tar.zst
933 MB
sha256:6dd13bb24530edb133b14a58338efb7bf754e6ae417c1f3ee78e7eba2cabe4d7