v1.7.x preview for @JosephTLyons #305
zed-zippy[bot]release.yml
on: push
check_scripts
1m 1s
create_draft_release
24s
compliance_check
3m 20s
bundle_windows_aarch64
34m 0s
bundle_windows_x86_64
32m 38s
push_release_update_notification
4s
Annotations
1 error and 9 warnings
|
compliance_check
Process completed with exit code 1.
|
|
run_tests_windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
run_tests_linux
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
run_tests_mac
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
bundle_linux_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: matbour/setup-sentry-cli@3e938c54b3018bdd019973689ef984e033b0454b. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
bundle_linux_aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: matbour/setup-sentry-cli@3e938c54b3018bdd019973689ef984e033b0454b. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
bundle_mac_aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, matbour/setup-sentry-cli@3e938c54b3018bdd019973689ef984e033b0454b. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
bundle_mac_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, matbour/setup-sentry-cli@3e938c54b3018bdd019973689ef984e033b0454b. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
bundle_windows_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: matbour/setup-sentry-cli@3e938c54b3018bdd019973689ef984e033b0454b. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
bundle_windows_aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: matbour/setup-sentry-cli@3e938c54b3018bdd019973689ef984e033b0454b. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 | |
|---|---|---|---|
|
Zed-aarch64.dmg
|
130 MB |
sha256:ba59a25e4daca11a5d45cc82f79b1be5810b47e83defb2c56985e7030440f41e
|
|
|
Zed-aarch64.exe
|
68.8 MB |
sha256:b05477a09ae91eb3500f816698a4a60fde147e60d7beb22679ce02ead6f9a568
|
|
|
Zed-x86_64.dmg
|
143 MB |
sha256:b7f733ae1a27d31bea5a0fcba7fc95c459e0b5533d9675f9bb72ea57470336e1
|
|
|
Zed-x86_64.exe
|
80.3 MB |
sha256:5e548d09c2252b7da35cb109e5bc7e8a86f84aebaa6468b3e3e961b07947d805
|
|
|
compliance-report-v1.7.0-pre.md
|
8.87 KB |
sha256:e424df143850948ef7f77384d07ebb55f258f615e95e370e275bd7221a0078b7
|
|
|
zed-linux-aarch64.tar.gz
|
135 MB |
sha256:c01fb977ed03c17f59f9d91984b12dfd5301a8dab0633fe14dd3975bc1a051ba
|
|
|
zed-linux-x86_64.tar.gz
|
140 MB |
sha256:774a98abd282a70c1468b5a93b4fbd7f7fa8af7d05eb7f9470e8ae0070a17082
|
|
|
zed-remote-server-linux-aarch64.gz
|
35.9 MB |
sha256:1b320b2d571345ef3ecf26e6e82c66a4f5afd5c944fe21edbbd3eaa076314a78
|
|
|
zed-remote-server-linux-x86_64.gz
|
38.5 MB |
sha256:6c8ebe072ea0488e85457bced91d0f56456a59a4541d29ebb977cc0c9d0f4a97
|
|
|
zed-remote-server-macos-aarch64.gz
|
32.5 MB |
sha256:fb6f506dc2309d41c2aecda67761a97d76e28abee99f4f0a4dd7dfd7a7c7ff14
|
|
|
zed-remote-server-macos-x86_64.gz
|
35.8 MB |
sha256:a6d0b1f235abdfc71b24c8345413d71129dc7fd94862c2e20635c1382ecedfd7
|
|
|
zed-remote-server-windows-aarch64.zip
|
33.4 MB |
sha256:44e23e8ed9f9c65025da1ffe99cf36f692f816ce04c311cfcb3a1b238d71a3e5
|
|
|
zed-remote-server-windows-x86_64.zip
|
35.3 MB |
sha256:4a824dee5b9034caf6f77b7d9d4ce7981c513be187813e892521adecbdc07c5e
|
|