wezterm/ci/macos-entitlement.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>com.apple.security.automation.apple-events</key>
    <true/>
    <key>com.apple.security.device.bluetooth</key>
    <true/>
</dict>
</plist>
macos: Add com.apple.security.automation.apple-events entitlement This is necessary for applications spawned via wezterm to be able to generate apple events. wezterm already had the text for the authorization prompt in its plist, but because it was code signed with the default set of entitlements, macOS didn't bother to prompt. This commit introduces an explicit set of entitlements and uses those when signing the executable. I test this by manually codesigning on my laptop and confirmed that I could run bbedit from inside wezterm. I can't directly test the CI version of that flow on my laptop as it may destroy my keychain if I got something wrong. We'll have to see if the CI generated build works out! refs: https://github.com/wez/wezterm/issues/2242 h/t to https://github.com/microsoft/vscode/issues/119787 for clearly documenting what was needed. 2022-07-16 05:33:30 +03:00			`<?xml version="1.0" encoding="UTF-8"?>`
			`<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">`
			`<plist version="1.0">`
			`<dict>`
			`<key>com.apple.security.automation.apple-events</key>`
			`<true/>`
macos: add bluetooth entitlement refs: https://github.com/wez/wezterm/issues/2330 2022-08-02 07:26:27 +03:00			`<key>com.apple.security.device.bluetooth</key>`
			`<true/>`
macos: Add com.apple.security.automation.apple-events entitlement This is necessary for applications spawned via wezterm to be able to generate apple events. wezterm already had the text for the authorization prompt in its plist, but because it was code signed with the default set of entitlements, macOS didn't bother to prompt. This commit introduces an explicit set of entitlements and uses those when signing the executable. I test this by manually codesigning on my laptop and confirmed that I could run bbedit from inside wezterm. I can't directly test the CI version of that flow on my laptop as it may destroy my keychain if I got something wrong. We'll have to see if the CI generated build works out! refs: https://github.com/wez/wezterm/issues/2242 h/t to https://github.com/microsoft/vscode/issues/119787 for clearly documenting what was needed. 2022-07-16 05:33:30 +03:00			`</dict>`
			`</plist>`