Workflow Perf Improvement and DRY refactor #33
app-build-release-artifacts.yml
on: pull_request
Matrix: build-app-release
Deployment protection rules
Reviewers, timers, and other rules protecting deployments in this run
| Event | Environments |
|---|---|
|
Keshav-writes-code
approved
|
production
and
|
Annotations
4 errors and 7 warnings
|
build-app-release (ubuntu-22.04-arm) / build
Command "bun ["tauri","build"]" failed with exit code 1
|
|
build-app-release (ubuntu-22.04) / build
Command "bun ["tauri","build"]" failed with exit code 1
|
|
build-app-release (windows-2022) / build
Command "bun ["tauri","build"]" failed with exit code 1
|
|
build-app-release (ubuntu-22.04, --apk --split-per-abi --target aarch64 --target armv7, android) / build
Command "bun ["tauri","android","build","--apk","--split-per-abi","--target","aarch64","--target","armv7"]" failed with exit code 1
|
|
build-app-release (ubuntu-22.04-arm) / build
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 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-app-release (ubuntu-22.04) / build
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 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-app-release (windows-2022) / build
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 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-app-release (ubuntu-22.04, --apk --split-per-abi --target aarch64 --target armv7, android) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, android-actions/setup-android@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/
|
|
build-app-release (macos-latest, --target aarch64-apple-darwin) / build
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 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-app-release (macos-latest, --target x86_64-apple-darwin) / build
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 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-app-release (windows-11-arm) / build
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 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 | |
|---|---|---|---|
|
cherit-v0.0.1-darwin-aarch64-release.app
|
4.35 MB |
sha256:292429b05c2d71bb1ae0cde887bb62bc587b9104fbf6794bc561f71cf38dd21a
|
|
|
cherit-v0.0.1-darwin-aarch64-release.dmg
|
5.96 MB |
sha256:9309afaa5022da23efaac7109332f1cff2deb11558e1fa3c90409375865aced3
|
|
|
cherit-v0.0.1-darwin-x64-release.app
|
4.44 MB |
sha256:f131cdf8e94124dc7794450d1e5992b664bf42cec9f5eab61ce84f7e0f71791d
|
|
|
cherit-v0.0.1-darwin-x64-release.dmg
|
6.08 MB |
sha256:030eae25517c61db43f0d80b2a0b8cb5033aad661ce25aeeade9d1b583c83917
|
|
|
cherit-v0.0.1-windows-arm64-release.exe
|
2.33 MB |
sha256:e9642753eed7b3794b1900622f49ca06766c5fb99b4b9c73cb3e12b26d2140ad
|
|
|
cherit-v0.0.1-windows-arm64-release.msi
|
3.03 MB |
sha256:1a22b16dcea62999af4fa52c0dd250921d4ef928196dfd4ae91021f88971b7a6
|
|