Skip to content

ghostty 1.3.1-paste.5

Pre-release
Pre-release

Choose a tag to compare

@xhqing xhqing released this 10 Nov 15:09
· 4 commits to main since this release
0b6a9b8

Warning: the Ghostty.app.zip attached to this release does not launch. The hardened runtime enabled library validation, which rejects Sparkle.framework for a self-signed certificate (no team ID). This release is kept for the record only — install v1.3.1-paste.6 instead.


Compile the default look and feel into the binary, and sign builds with a fixed self-signed certificate.

New: default look and feel compiled into the binary (works out of the box, defaults no longer come from a file anything can rewrite)

  • Why: Ghostty takes its entire configuration from files on disk, so the terminal's look has to be rebuilt by hand after switching machines or reinstalling; and any program able to write ~/.config/ghostty/config can casually change those defaults (the two-way interference happened with cmux reading the same file — see Issue #24 and xhqing/cmux#70).
  • What changed: (1) Added src/config/config-builtin.ghostty (9 look-and-feel defaults: theme, font family, font size, cursor, shell integration), loaded first via @embedFile in Config.loadDefaultFiles() — it is the lowest-priority layer, since every user config file (XDG / App Support) loads after it and naturally overrides it; when config-default-files = false this layer is dropped together with the user configs, so the semantics are unchanged. (2) The built-in config carries only machine-independent values: window size / position and every keybind (the Quick Terminal global: hotkey, the super+v image-paste patch) still belong to the user config file. (3) Added Zig unit tests: the built-in file must parse, and a user config loaded later must override it.
  • Boundaries: (1) theme = GitHub Dark Default relies on the theme directory bundled with the app (Contents/Resources/ghostty/themes; emit-themes defaults to true, so no extra packaging is needed). (2) A machine that has never created a config file still gets the commented template on first launch (existing behavior); the built-in values take effect on top of that template.

Changed: builds are signed with a fixed self-signed certificate, so the Accessibility grant no longer dies with every build

  • Why: This fork's artifacts were ad-hoc signed, and macOS TCC matches the Accessibility grant for an ad-hoc signed app by its signature hash (cdhash) — every rebuild changes the hash, the system treats it as a different app, and the previous grant is silently revoked (measured 2026-09-22: right after installing a new build, osascript inside the terminal failed with not allowed to send keystrokes (1002), and the only recovery was tccutil reset plus re-granting by hand; Issue #2).
  • What changed: (1) build.yml gained a certificate-signing path: it imports the fixed self-signed certificate from secrets (a .p12) into a throwaway keychain, marks trust for the code-signing policy only, signs the nested Sparkle components one by one and then the app itself, verifies the signature and prints the designated requirement, and deletes the keychain when the build finishes. When the secrets are unavailable (pull requests from forks) it falls back to ad-hoc so CI still produces artifacts. (2) Added SIGNING.md covering what the certificate is for, the secret names, and why it must not be casually regenerated. (3) Removed the upstream leftover workflows: vouch-check-pr.yml / milestone.yml (which used pull_request_target), the vouch-* family, and release-tag.yml, release-tip.yml, publish-tag.yml, flatpak.yml, snap.yml, nix.yml, test.yml, update-colorschemes.yml (which depended on upstream's Namespace runners, Nix, its own CDN and minisign) — in this repository they either always skip or only ever fail, so build.yml is now the single CI workflow.
  • Boundaries: (1) The self-signed certificate is not in Apple's trust chain and the app is not notarized, so Gatekeeper still requires a manual allow on first launch (same as ad-hoc, not a regression). (2) Once the certificate is in use, do not regenerate it — changing it means changing the signing identity, and every machine has to re-grant Accessibility once. (3) Builds from this branch are the paired test: codesign -dv should report the certificate identity (Authority=Ghostty Fork Self-Signed) instead of Signature=adhoc; the Accessibility grant is re-tested after installing the next Release.