Skip to content

v1.4.13

Choose a tag to compare

View all tags
@github-actions github-actions released this 04 Oct 17:20
v1.4.13
b709cf2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This release has the same upstream base as v1.4.12, upstream Zed as of 2026-10-03 (zed-industries@a84689073d).

Fork changes

Fixed

  • Zed crashing when you double-clicked a tab. Since zed-industries/zed#65081, which v1.4.12 brought in, an editor tab reads its pane to build its extra context menu actions. The double-click handler asked for those actions while it was still updating that pane, and gpui aborted the process. Markdown preview tabs did the same. Zed now looks up the actions after the click handler finishes. (kjanat/zed-editor#169, closes kjanat/zed-editor#168)
  • script/uninstall.sh deleting the wrong paths when $HOME contains a space. With HOME=/Users/John Doe, rm -rf received /Users/John and Doe/.zed_server as two paths. The script now quotes the path.

Language servers

  • When a language server writes plain text to stdout and exits, the error in the status and the log includes up to 512 characters of that text after Server reset the connection:. A misconfigured wrapper, such as mise task -- roslyn printing task info, showed only Server reset the connection before. (kjanat/zed-editor#169)
  • When a server drops the connection during initialize, Zed waits up to 2s for its stdout and stderr to finish before reporting the failure, so stderr from that window reaches the failure status. Stderr after an initialize timeout or error response can still be lost, tracked in kjanat/zed-editor#170. (kjanat/zed-editor#169)
  • Zed skips the shutdown request for a server whose stdout already closed. After a failed start, the log has no Shutdown request failure errors. (kjanat/zed-editor#169)

Builds and releases

  • Each release includes debug symbols for every platform. They turn crash dumps and stack traces into function names and line numbers. The release workflow attests them like the other assets. (kjanat/zed-editor#169)
    • zed-windows-<arch>.dbg.zip: PDB files for Zed, the CLI, the auto-update helper, the Explorer context menu handler and the remote server.
    • zed-linux-<arch>.dbg.tar.gz: DWARF for Zed and the remote server (zed.dbg, remote_server.dbg).
    • zed-macos-<arch>.dwarf.tar.gz: DWARF for Zed and the remote server (zed.dwarf, remote_server.dwarf).
  • The LLVM 23.1.2 release ld.lld needs ICU 70, which only GitHub's Ubuntu 24.04 amd64 image installs. The FreeBSD and Linux bundle jobs now install Ubuntu 22.04's libicu70, pinned by SHA-512.
  • A dispatched release run reuses the tag's draft release and creates one only when none exists.

CI and scripts

  • script/release-notes/linkify.py rewrites issue, pull request and commit references in release notes as explicit links, which Zed's in-app release notes view needs. It asks GitHub whether each number is an issue or a pull request, and links a bare SHA to upstream when upstream's default branch contains it. script/release-notes/publish.bash linkifies a notes file, sets it as the release body and uploads the matching notes.json.
  • script/mitm-proxy.sh stops its mitmproxy container on every exit, including a failing cargo run or closed stdin.
  • script/upstream-sync/test_resolve.py accepts any pinned commit SHA for the resolver's actions, and an action pin bump passes sync_security.
  • Every script with a shebang is executable, among them script/pacman/zed.sh and the GitHub triage scripts under script/.

Full Changelog: v1.4.12...v1.4.13

Assets 30
Loading