Sąraše – 2 versijos programos Emdash, nuo 2026 m. spalio 30 d. iki dabartinės 1.2.11. Kiekviena veda į diegimo failus leidėjo serveryje.
| Versija | Data | Dydis | Failai |
|---|---|---|---|
| 1.2.11Naujausia | 2026 m. lapkričio 6 d. | — | 64 bitų EXE (NSIS)64 bitų MSI64 bitų EXE (NSIS) Laidos pastabosThis release improves Git authentication, Windows compatibility, and SSH responsiveness. It also reduces background fetch overhead, fixes pane shortcuts after switching tasks, and adds an in-app signup for Emdash 2.0 early access.
Highlights
- The project's Git credentials setting now applies to Emdash's own local Git operations, including push, pull, and fetch. Choosing System uses the machine's credentials, while an account explicitly selected for an operation still takes precedence.
- Join the Emdash 2.0 waitlist directly from the sidebar, with your email and an optional note about your team or workflow. The card can be dismissed for the current release.
Fixes
- Commit & Push and other Git network operations on Windows authenticate correctly through the connected account, fixing failures where pushing from a terminal worked but pushing from Emdash did not.
- Agent hooks on Windows run correctly when launched through Git Bash, including Claude Code hooks. Prompt and assistant text passed to hooks is no longer misinterpreted as shell commands.
- Windows builds resolve the bundled SSH dependency correctly, fixing a module-loading error reported in v1.2.10.
- SSH connections send handshake and interactive traffic without waiting for TCP buffering, improving responsiveness when connecting to and working on remote machines.
- Background Git fetches wait after the previous fetch finishes and back off when a repository is slow. Fetches also avoid unnecessary metadata writes and automatic maintenance, reducing disk work and contention with other Git operations.
- Self-hosted Git integrations correctly match remotes that use custom HTTP or HTTPS ports, including Forgejo instances.
- Pane shortcuts remain active after switching tasks or projects when a terminal or input has already received focus. |
| 1.2.10 | 2026 m. spalio 30 d. | — | 64 bitų MSI64 bitų EXE (NSIS)64 bitų EXE (NSIS) Laidos pastabosThis release lets you trust repositories that Git refuses because of their ownership, stops background processes from opening console windows on Windows, and keeps large repositories responsive. It also fixes Clean Artifacts, Git SSH configuration, credential handling, and panel sizes. Remote machines get these fixes once you update their workspace server in Settings > Machines.
Highlights
- When Git refuses a repository because another user owns it, such as a repository in a WSL folder, Add Project explains why and shows the Git command to run yourself. Trust Repository adds that one folder to your global Git configuration after confirmation, which also applies to agents and terminals. For SSH projects, the entry is written on the remote machine.
- On Windows, Git, agents, SSH connections, and other background processes no longer open console windows or Windows Terminal tabs.
- Changed-file diffs load while background Git work runs and show a loading state or error instead of a blank pane. If a reload fails, the last loaded diff stays visible and read-only until it recovers.
- The Workspaces tab measures disk usage much faster, counts worktrees inside their repository only once, reuses results for five minutes, and stops scanning when you leave the view.
- Creating tasks on large repositories, re-provisioning, deleting tasks and workspaces, updating pull request checkouts, and other long-running workspace operations no longer fail after 30 seconds while the machine is still working on them.
Fixes
- Clean Artifacts in the Workspaces tab removes ignored build output in place instead of removing the worktree. Tracked files, uncommitted and untracked changes, local .env files, files matching your preserve patterns, nested workspaces, and linked tasks all stay. Emdash won't clean a workspace while agents or terminals are running in it, and the action is available for local workspaces.
- Clones and other Git operations use the core.sshCommand from your Git configuration, so SSH key routers and per-host keys work.
- Git credential requests bypass proxy settings. When a credential read fails, for example in a tmux session reattached after Emdash restarted, Git prints the reason before prompting.
- New tmux tasks get their own environment and no longer inherit stale variables or credentials from earlier sessions. Credential tokens and environment values stay out of process arguments, where other users on a shared machine could read them.
- Creating a worktree recovers from worktrees deleted outside Emdash without running git worktree prune by hand. Git failures show Git's message instead of a bare exit code, with credential URLs and tokens removed. Deleting a worktree whose branch is already gone succeeds.
- The sidebars and terminal drawer keep the size you set when the window resizes, including when a tiling window manager rearranges windows, and return to it after a small window grows again.
- When the default branch can't be resolved, Create Task explains that you need to select a branch in workspace settings. Automations show the same reason, and changing an automation's schedule saves only the schedule.
- On Linux and Windows with Watchman running, Emdash watches Git metadata with the system file watcher, so Watchman no longer crawls the .git directory.
- Agents on Windows no longer create a stray %SystemDrive%\ProgramData folder tree in their working directory, and they receive the system and program folder variables that .NET and NuGet need.
- The Linux .deb and .rpm packages declare ALSA and GBM as dependencies, so the app starts on minimal installs.
- Crash-loop recovery shows why the most recent launch failed.
- Stored notifications are trimmed to the newest 500 on launch, as intended. |