You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Fixed
The certificate-signed build launches again. The signing step enabled the hardened runtime, and hardened runtime turns on library validation: a loaded dylib has to share the main executable's Team ID. A self-signed certificate has no team ID, so dyld refused to load Sparkle.framework (mapping process and mapped file (non-platform) have different Team IDs) and the app died on launch. The signing step no longer passes --options runtime. This fork is not notarized, so the hardened runtime bought nothing, and the earlier ad-hoc builds never used it either.
Notes
The asset published with v1.3.1-paste.5 could not launch. That release is now marked as a pre-release and kept for the record only — install this version instead.
Verified on the released build: flags=0x0(none), Authority=Ghostty Fork Self-Signed, codesign --verify --deep --strict passes, ghostty +show-config prints the builtin defaults and +validate-config is silent. The designated requirement is identical to the paste.5 build, so the Accessibility identity does not change.