v1.3.2

Rune v1.3.2

This patch release tightens security around workspace config and command approvals, and fixes several crashes.

Security

• A repository's workspace config now needs your trust before it applies. Opening a repository that has a .rune/config.yaml no longer applies that file automatically. Rune shows you the file and asks you to trust, trust once or ignore it. It asks again whenever the file changes. You can review or revoke the decision with authorizer list and authorizer revoke.
• Remote workspaces ignore the project config. A remote machine never applies the gui.env from a project's .rune/config.yaml, because it can't ask you to trust that file.
• Command approvals now apply to the exact program you approved. Approving git status no longer also allows a local ./git, a different git earlier on your PATH, or the same program run through a wrapper like env, xargs or sudo. If an approved program's file changes, Rune asks you to renew the approval, allow it once or deny it.
• Approvals saved by earlier versions have been reset. Those approvals covered more than the prompt showed. Rune lets you know when this happens.
• Package signatures are checked only against signing keys built into Rune.

Improvements

• Choose what Always and Never cover. The command approval prompt has a new scope picker, so you decide which programs an "Always" or "Never" answer applies to.
• Approve programs that aren't installed yet. Commands whose program isn't on the system, such as timeout on macOS, can now be approved instead of prompting every time.

Fixes

• Fixed a crash when pressing Backspace in the command prompt after an argument containing a line break, such as a pasted script.
• Fixed a GUI crash on startup on Linux when no display is available. Rune now says why it can't open a window and suggests --tui or --headless.
• Fixed a crash when accepting the rune-agent install prompt while the docs workspace notice was open.

Full Changelog: v1.3.1...v1.3.2