v0.36.5

PolterType v0.36.5

No signing identity. The MSI / DMG / AppImage below are
produced by CI on fdd87a8f5125540d8e81a03e322fef2ed528b421. The macOS bundle is
ad-hoc signed — which is what lets it hold Accessibility
permission, not a statement about who built it — and
nothing is notarised; the Windows installer is unsigned. So
both still warn on first launch — see the workarounds below.

Install

• Windows — download the .msi and double-click. Per-user
  install, no admin rights needed. SmartScreen may say
  "Windows protected your PC"; click More info →
  Run anyway.
• macOS — download the .dmg, drag poltertype.app into
  /Applications. First launch shows "PolterType cannot be
  opened because the developer cannot be verified" — right-
  click the app and pick Open, or run
  xattr -dr com.apple.quarantine /Applications/poltertype.app
  once. Then grant Accessibility permission in System
  Settings — again after every update, since without a
  Developer ID macOS identifies the app by the hash of its
  own bytes and reads a new version as different software.
• Linux — download the .AppImage for your
  architecture (x86_64 for a normal PC, aarch64 for a
  Raspberry Pi 5, an Asahi Mac or an ARM server),
  chmod +x it, run. On Wayland sessions, see
  docs/PERMISSIONS.md for the evdev permission setup.

See CHANGELOG.md for the full list of changes.

Full Changelog: v0.36.4...v0.36.5

v0.36.4

PolterType v0.36.4

No signing identity. The MSI / DMG / AppImage below are
produced by CI on 076484d1ea389cbc10f8f29dd7582f6f469374b6. The macOS bundle is
ad-hoc signed — which is what lets it hold Accessibility
permission, not a statement about who built it — and
nothing is notarised; the Windows installer is unsigned. So
both still warn on first launch — see the workarounds below.

Install

• Windows — download the .msi and double-click. Per-user
  install, no admin rights needed. SmartScreen may say
  "Windows protected your PC"; click More info →
  Run anyway.
• macOS — download the .dmg, drag poltertype.app into
  /Applications. First launch shows "PolterType cannot be
  opened because the developer cannot be verified" — right-
  click the app and pick Open, or run
  xattr -dr com.apple.quarantine /Applications/poltertype.app
  once. Then grant Accessibility permission in System
  Settings — again after every update, since without a
  Developer ID macOS identifies the app by the hash of its
  own bytes and reads a new version as different software.
• Linux — download the .AppImage for your
  architecture (x86_64 for a normal PC, aarch64 for a
  Raspberry Pi 5, an Asahi Mac or an ARM server),
  chmod +x it, run. On Wayland sessions, see
  docs/PERMISSIONS.md for the evdev permission setup.

See CHANGELOG.md for the full list of changes.

Full Changelog: v0.36.3...v0.36.4

v0.36.3

PolterType v0.36.3

No signing identity. The MSI / DMG / AppImage below are
produced by CI on 1c0b170dfdbee3fbd85bc00e07f4cc6ba751ef31. The macOS bundle is
ad-hoc signed — which is what lets it hold Accessibility
permission, not a statement about who built it — and
nothing is notarised; the Windows installer is unsigned. So
both still warn on first launch — see the workarounds below.

Install

• Windows — download the .msi and double-click. Per-user
  install, no admin rights needed. SmartScreen may say
  "Windows protected your PC"; click More info →
  Run anyway.
• macOS — download the .dmg, drag poltertype.app into
  /Applications. First launch shows "PolterType cannot be
  opened because the developer cannot be verified" — right-
  click the app and pick Open, or run
  xattr -dr com.apple.quarantine /Applications/poltertype.app
  once. Then grant Accessibility permission in System
  Settings — again after every update, since without a
  Developer ID macOS identifies the app by the hash of its
  own bytes and reads a new version as different software.
• Linux — download the .AppImage for your
  architecture (x86_64 for a normal PC, aarch64 for a
  Raspberry Pi 5, an Asahi Mac or an ARM server),
  chmod +x it, run. On Wayland sessions, see
  docs/PERMISSIONS.md for the evdev permission setup.

See CHANGELOG.md for the full list of changes.

Full Changelog: v0.36.2...v0.36.3

v0.36.2

PolterType v0.36.2

No signing identity. The MSI / DMG / AppImage below are
produced by CI on e7cd79b24310210a7a2e9266f5f867a092f2d213. The macOS bundle is
ad-hoc signed — which is what lets it hold Accessibility
permission, not a statement about who built it — and
nothing is notarised; the Windows installer is unsigned. So
both still warn on first launch — see the workarounds below.

Install

• Windows — download the .msi and double-click. Per-user
  install, no admin rights needed. SmartScreen may say
  "Windows protected your PC"; click More info →
  Run anyway.
• macOS — download the .dmg, drag poltertype.app into
  /Applications. First launch shows "PolterType cannot be
  opened because the developer cannot be verified" — right-
  click the app and pick Open, or run
  xattr -dr com.apple.quarantine /Applications/poltertype.app
  once. Then grant Accessibility permission in System
  Settings — again after every update, since without a
  Developer ID macOS identifies the app by the hash of its
  own bytes and reads a new version as different software.
• Linux — download the .AppImage for your
  architecture (x86_64 for a normal PC, aarch64 for a
  Raspberry Pi 5, an Asahi Mac or an ARM server),
  chmod +x it, run. On Wayland sessions, see
  docs/PERMISSIONS.md for the evdev permission setup.

See CHANGELOG.md for the full list of changes.

Full Changelog: v0.36.1...v0.36.2

v0.36.1

PolterType v0.36.1

No signing identity. The MSI / DMG / AppImage below are
produced by CI on bee6ccf3e69418cb37d9d176c33a6b686f88b02a. The macOS bundle is
ad-hoc signed — which is what lets it hold Accessibility
permission, not a statement about who built it — and
nothing is notarised; the Windows installer is unsigned. So
both still warn on first launch — see the workarounds below.

Install

• Windows — download the .msi and double-click. Per-user
  install, no admin rights needed. SmartScreen may say
  "Windows protected your PC"; click More info →
  Run anyway.
• macOS — download the .dmg, drag poltertype.app into
  /Applications. First launch shows "PolterType cannot be
  opened because the developer cannot be verified" — right-
  click the app and pick Open, or run
  xattr -dr com.apple.quarantine /Applications/poltertype.app
  once. Then grant Accessibility permission in System
  Settings — again after every update, since without a
  Developer ID macOS identifies the app by the hash of its
  own bytes and reads a new version as different software.
• Linux — download the .AppImage for your
  architecture (x86_64 for a normal PC, aarch64 for a
  Raspberry Pi 5, an Asahi Mac or an ARM server),
  chmod +x it, run. On Wayland sessions, see
  docs/PERMISSIONS.md for the evdev permission setup.

See CHANGELOG.md for the full list of changes.

Full Changelog: v0.36.0...v0.36.1

v0.36.0

PolterType v0.36.0

No signing identity. The MSI / DMG / AppImage below are
produced by CI on e6fdfc9fc4d548f62b83602ebae7c7b9fd4870c0. The macOS bundle is
ad-hoc signed — which is what lets it hold Accessibility
permission, not a statement about who built it — and
nothing is notarised; the Windows installer is unsigned. So
both still warn on first launch — see the workarounds below.

Install

• Windows — download the .msi and double-click. Per-user
  install, no admin rights needed. SmartScreen may say
  "Windows protected your PC"; click More info →
  Run anyway.
• macOS — download the .dmg, drag poltertype.app into
  /Applications. First launch shows "PolterType cannot be
  opened because the developer cannot be verified" — right-
  click the app and pick Open, or run
  xattr -dr com.apple.quarantine /Applications/poltertype.app
  once. Then grant Accessibility permission in System
  Settings — again after every update, since without a
  Developer ID macOS identifies the app by the hash of its
  own bytes and reads a new version as different software.
• Linux — download the .AppImage for your
  architecture (x86_64 for a normal PC, aarch64 for a
  Raspberry Pi 5, an Asahi Mac or an ARM server),
  chmod +x it, run. On Wayland sessions, see
  docs/PERMISSIONS.md for the evdev permission setup.

See CHANGELOG.md for the full list of changes.

Full Changelog: v0.35.0...v0.36.0

v0.35.0

PolterType v0.35.0

No signing identity. The MSI / DMG / AppImage below are
produced by CI on 812a0c8c4f6d1228943900d4b5360bf9b7c3ca63. The macOS bundle is
ad-hoc signed — which is what lets it hold Accessibility
permission, not a statement about who built it — and
nothing is notarised; the Windows installer is unsigned. So
both still warn on first launch — see the workarounds below.

Install

• Windows — download the .msi and double-click. Per-user
  install, no admin rights needed. SmartScreen may say
  "Windows protected your PC"; click More info →
  Run anyway.
• macOS — download the .dmg, drag poltertype.app into
  /Applications. First launch shows "PolterType cannot be
  opened because the developer cannot be verified" — right-
  click the app and pick Open, or run
  xattr -dr com.apple.quarantine /Applications/poltertype.app
  once. Then grant Accessibility permission in System
  Settings — again after every update, since without a
  Developer ID macOS identifies the app by the hash of its
  own bytes and reads a new version as different software.
• Linux — download the .AppImage for your
  architecture (x86_64 for a normal PC, aarch64 for a
  Raspberry Pi 5, an Asahi Mac or an ARM server),
  chmod +x it, run. On Wayland sessions, see
  docs/PERMISSIONS.md for the evdev permission setup.

See CHANGELOG.md for the full list of changes.

Full Changelog: v0.34.1...v0.35.0

v0.34.1

PolterType v0.34.1

No signing identity. The MSI / DMG / AppImage below are
produced by CI on f6d5eb3047315f11edd20fe8df2622b67c0597d8. The macOS bundle is
ad-hoc signed — which is what lets it hold Accessibility
permission, not a statement about who built it — and
nothing is notarised; the Windows installer is unsigned. So
both still warn on first launch — see the workarounds below.

Install

• Windows — download the .msi and double-click. Per-user
  install, no admin rights needed. SmartScreen may say
  "Windows protected your PC"; click More info →
  Run anyway.
• macOS — download the .dmg, drag poltertype.app into
  /Applications. First launch shows "PolterType cannot be
  opened because the developer cannot be verified" — right-
  click the app and pick Open, or run
  xattr -dr com.apple.quarantine /Applications/poltertype.app
  once. Then grant Accessibility permission in System
  Settings — again after every update, since without a
  Developer ID macOS identifies the app by the hash of its
  own bytes and reads a new version as different software.
• Linux — download the .AppImage for your
  architecture (x86_64 for a normal PC, aarch64 for a
  Raspberry Pi 5, an Asahi Mac or an ARM server),
  chmod +x it, run. On Wayland sessions, see
  docs/PERMISSIONS.md for the evdev permission setup.

See CHANGELOG.md for the full list of changes.

What's Changed

• engine: force-by-selection follows the text, not the current layout by @iga566-gh in #68
• windows: the low-level hook's modifier snapshot describes the event, not the moment before it by @iga566-gh in #69

Full Changelog: v0.34.0...v0.34.1

v0.34.0

PolterType v0.34.0

No signing identity. The MSI / DMG / AppImage below are
produced by CI on 6b2b14e56ef525fd526fa069db2137ec1256daac. The macOS bundle is
ad-hoc signed — which is what lets it hold Accessibility
permission, not a statement about who built it — and
nothing is notarised; the Windows installer is unsigned. So
both still warn on first launch — see the workarounds below.

Install

• Windows — download the .msi and double-click. Per-user
  install, no admin rights needed. SmartScreen may say
  "Windows protected your PC"; click More info →
  Run anyway.
• macOS — download the .dmg, drag poltertype.app into
  /Applications. First launch shows "PolterType cannot be
  opened because the developer cannot be verified" — right-
  click the app and pick Open, or run
  xattr -dr com.apple.quarantine /Applications/poltertype.app
  once. Then grant Accessibility permission in System
  Settings — again after every update, since without a
  Developer ID macOS identifies the app by the hash of its
  own bytes and reads a new version as different software.
• Linux — download the .AppImage for your
  architecture (x86_64 for a normal PC, aarch64 for a
  Raspberry Pi 5, an Asahi Mac or an ARM server),
  chmod +x it, run. On Wayland sessions, see
  docs/PERMISSIONS.md for the evdev permission setup.

See CHANGELOG.md for the full list of changes.

Full Changelog: v0.33.2...v0.34.0

v0.33.2

PolterType v0.33.2

No signing identity. The MSI / DMG / AppImage below are
produced by CI on 481634051b343afa8358a66a5ebb8bce09edab5d. The macOS bundle is
ad-hoc signed — which is what lets it hold Accessibility
permission, not a statement about who built it — and
nothing is notarised; the Windows installer is unsigned. So
both still warn on first launch — see the workarounds below.

Install

• Windows — download the .msi and double-click. Per-user
  install, no admin rights needed. SmartScreen may say
  "Windows protected your PC"; click More info →
  Run anyway.
• macOS — download the .dmg, drag poltertype.app into
  /Applications. First launch shows "PolterType cannot be
  opened because the developer cannot be verified" — right-
  click the app and pick Open, or run
  xattr -dr com.apple.quarantine /Applications/poltertype.app
  once. Then grant Accessibility permission in System
  Settings — again after every update, since without a
  Developer ID macOS identifies the app by the hash of its
  own bytes and reads a new version as different software.
• Linux — download the .AppImage for your
  architecture (x86_64 for a normal PC, aarch64 for a
  Raspberry Pi 5, an Asahi Mac or an ARM server),
  chmod +x it, run. On Wayland sessions, see
  docs/PERMISSIONS.md for the evdev permission setup.

See CHANGELOG.md for the full list of changes.

Full Changelog: v0.33.1...v0.33.2