Skip to content

release: v2.11.0

release: v2.11.0 #42

Re-run triggered March 16, 2026 13:26
Status Failure
Total duration 1d 0h 0m 4s
Artifacts

publish.yml

on: push
Upload release to PyPI
23s
Upload release to PyPI
Matrix: Build Binaries
Build AppImage
0s
Build AppImage
Build Snap Package
3m 56s
Build Snap Package
Build Flatpak
31s
Build Flatpak
Update Homebrew Formula
6s
Update Homebrew Formula
Publish to AUR
43s
Publish to AUR
Update Scoop Manifest
0s
Update Scoop Manifest
Update Winget Manifest
0s
Update Winget Manifest
Create GitHub Release
0s
Create GitHub Release
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 7 warnings
Build Binaries (macos-latest, arm64, weeb-cli-macOS-arm64, weeb-cli)
Process completed with exit code 1.
Build Binaries (ubuntu-latest, x64, weeb-cli-Linux-x86_64, weeb-cli)
The strategy configuration was canceled because "build_binaries.macos-latest_arm64_weeb-c" failed
Build Binaries (ubuntu-latest, x64, weeb-cli-Linux-x86_64, weeb-cli)
Process completed with exit code 1.
Build Binaries (macos-15, x64, weeb-cli-macOS-x86_64, weeb-cli)
The strategy configuration was canceled because "build_binaries.macos-latest_arm64_weeb-c" failed
Build Binaries (macos-15, x64, weeb-cli-macOS-x86_64, weeb-cli)
The operation was canceled.
Build Binaries (windows-latest, x64, weeb-cli-Windows-x86_64.exe, weeb-cli.exe)
The strategy configuration was canceled because "build_binaries.macos-latest_arm64_weeb-c" failed
Build Binaries (windows-latest, x86, weeb-cli-Windows-x86.exe, weeb-cli.exe)
The strategy configuration was canceled because "build_binaries.macos-latest_arm64_weeb-c" failed
Build Flatpak
Process completed with exit code 1.
Build Snap Package
The process '/usr/bin/sudo' failed with exit code 1
Build AppImage
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Build Binaries (macos-latest, arm64, weeb-cli-macOS-arm64, weeb-cli)
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 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 Binaries (ubuntu-latest, x64, weeb-cli-Linux-x86_64, weeb-cli)
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 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 Binaries (macos-15, x64, weeb-cli-macOS-x86_64, weeb-cli)
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 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 Binaries (windows-latest, x64, weeb-cli-Windows-x86_64.exe, weeb-cli.exe)
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 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 Binaries (windows-latest, x86, weeb-cli-Windows-x86.exe, weeb-cli.exe)
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 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 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 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 Snap Package
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, snapcore/action-build@v1. 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/