v1.6.0

What's Changed

• chore: just sign-server / sign-check for the release signing tunnel by @thewh1teagle in #43
• release: v1.6.0 — selections that scroll, and copies that paste right by @thewh1teagle in #42

Full Changelog: v1.5.0...v1.6.0

v1.5.0

What's Changed

• release: v1.5.0 — closing a busy tab asks first by @thewh1teagle in #39

Full Changelog: v1.4.0...v1.5.0

Platform support

macOS — tested. This is terra's development and v1 target. The
.dmg and the .app inside it are ad-hoc signed, not notarised, so
Gatekeeper shows the unidentified-developer prompt on first launch:
right-click the app and choose Open.

Linux (x86_64) and Windows (x86_64) — build-verified only. The
installers (.deb, -setup.exe) compile, pass the test suite and
pass clippy in CI, but the GUI has had far less real-world use than
on macOS. Bug reports welcome. The Windows installer is unsigned, so
SmartScreen will warn on first run — choose "More info" → "Run
anyway".

Every installer puts both halves of terra in place: terra-app (the
GUI) and terra (the CLI, needed for terra ls, terra new,
terra learn). On Linux and Windows both land on your PATH. On
macOS the CLI lives inside the bundle, at
/Applications/Terra.app/Contents/MacOS/terra — the install script
symlinks it into /usr/local/bin; if you installed by dragging the
.dmg, link it yourself:

ln -sf /Applications/Terra.app/Contents/MacOS/terra /usr/local/bin/terra

v1.4.0

What's Changed

• release: v1.4.0 — mouse selection in tmux, bracketed paste, focus follows the pointer by @thewh1teagle in #37
• ci: platform-true paste-test modifiers, tmux on runners, release runbook by @thewh1teagle in #38

Full Changelog: v1.3.2...v1.4.0

Platform support

macOS — tested. This is terra's development and v1 target. The
.dmg and the .app inside it are ad-hoc signed, not notarised, so
Gatekeeper shows the unidentified-developer prompt on first launch:
right-click the app and choose Open.

Linux (x86_64) and Windows (x86_64) — build-verified only. The
installers (.deb, -setup.exe) compile, pass the test suite and
pass clippy in CI, but the GUI has had far less real-world use than
on macOS. Bug reports welcome. The Windows installer is unsigned, so
SmartScreen will warn on first run — choose "More info" → "Run
anyway".

Every installer puts both halves of terra in place: terra-app (the
GUI) and terra (the CLI, needed for terra ls, terra new,
terra learn). On Linux and Windows both land on your PATH. On
macOS the CLI lives inside the bundle, at
/Applications/Terra.app/Contents/MacOS/terra — the install script
symlinks it into /usr/local/bin; if you installed by dragging the
.dmg, link it yourself:

ln -sf /Applications/Terra.app/Contents/MacOS/terra /usr/local/bin/terra

v1.3.2

What's Changed

• release: v1.3.2 — the last tab's close button asks too by @thewh1teagle in #35

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

v1.3.1

What's Changed

• packaging: give the NSIS installer the terra icon by @thewh1teagle in #33
• release: v1.3.1 — Windows polish, and quits that bypass the close dialog by @thewh1teagle in #34

Full Changelog: v1.3.0...v1.3.1

Platform support

macOS — tested. This is terra's development and v1 target. The
.dmg and the .app inside it are ad-hoc signed, not notarised, so
Gatekeeper shows the unidentified-developer prompt on first launch:
right-click the app and choose Open.

Linux (x86_64) and Windows (x86_64) — build-verified only. The
installers (.deb, -setup.exe) compile, pass the test suite and
pass clippy in CI, but the GUI has had far less real-world use than
on macOS. Bug reports welcome. The Windows installer is unsigned, so
SmartScreen will warn on first run — choose "More info" → "Run
anyway".

Every installer puts both halves of terra in place: terra-app (the
GUI) and terra (the CLI, needed for terra ls, terra new,
terra learn). On Linux and Windows both land on your PATH. On
macOS the CLI lives inside the bundle, at
/Applications/Terra.app/Contents/MacOS/terra — the install script
symlinks it into /usr/local/bin; if you installed by dragging the
.dmg, link it yourself:

ln -sf /Applications/Terra.app/Contents/MacOS/terra /usr/local/bin/terra

v1.3.0

What's Changed

• release: v1.3.0 — confirm before closing a window with running work by @thewh1teagle in #32

Full Changelog: v1.2.0...v1.3.0

Platform support

macOS — tested. This is terra's development and v1 target. The
.dmg and the .app inside it are ad-hoc signed, not notarised, so
Gatekeeper shows the unidentified-developer prompt on first launch:
right-click the app and choose Open.

Linux (x86_64) and Windows (x86_64) — build-verified only. The
installers (.deb, -setup.exe) compile, pass the test suite and
pass clippy in CI, but the GUI has had far less real-world use than
on macOS. Bug reports welcome. The Windows installer is unsigned, so
SmartScreen will warn on first run — choose "More info" → "Run
anyway".

Every installer puts both halves of terra in place: terra-app (the
GUI) and terra (the CLI, needed for terra ls, terra new,
terra learn). On Linux and Windows both land on your PATH. On
macOS the CLI lives inside the bundle, at
/Applications/Terra.app/Contents/MacOS/terra — the install script
symlinks it into /usr/local/bin; if you installed by dragging the
.dmg, link it yourself:

ln -sf /Applications/Terra.app/Contents/MacOS/terra /usr/local/bin/terra

v1.2.0

What's Changed

• release: v1.2.0 — terra transcript, shift-select in mouse-mode apps by @thewh1teagle in #31

Full Changelog: v1.1.0...v1.2.0

Platform support

macOS — tested. This is terra's development and v1 target. The
.dmg and the .app inside it are ad-hoc signed, not notarised, so
Gatekeeper shows the unidentified-developer prompt on first launch:
right-click the app and choose Open.

Linux (x86_64) and Windows (x86_64) — build-verified only. The
installers (.deb, -setup.exe) compile, pass the test suite and
pass clippy in CI, but the GUI has had far less real-world use than
on macOS. Bug reports welcome. The Windows installer is unsigned, so
SmartScreen will warn on first run — choose "More info" → "Run
anyway".

Every installer puts both halves of terra in place: terra-app (the
GUI) and terra (the CLI, needed for terra ls, terra new,
terra learn). On Linux and Windows both land on your PATH. On
macOS the CLI lives inside the bundle, at
/Applications/Terra.app/Contents/MacOS/terra — the install script
symlinks it into /usr/local/bin; if you installed by dragging the
.dmg, link it yourself:

ln -sf /Applications/Terra.app/Contents/MacOS/terra /usr/local/bin/terra

v1.1.0

What's Changed

• release: v1.1.0 — edit settings with agents, tab bar polish by @thewh1teagle in #30

Full Changelog: v1.0.3...v1.1.0

Platform support

macOS — tested. This is terra's development and v1 target. The
.dmg and the .app inside it are ad-hoc signed, not notarised, so
Gatekeeper shows the unidentified-developer prompt on first launch:
right-click the app and choose Open.

Linux (x86_64) and Windows (x86_64) — build-verified only. The
installers (.deb, -setup.exe) compile, pass the test suite and
pass clippy in CI, but the GUI has had far less real-world use than
on macOS. Bug reports welcome. The Windows installer is unsigned, so
SmartScreen will warn on first run — choose "More info" → "Run
anyway".

Every installer puts both halves of terra in place: terra-app (the
GUI) and terra (the CLI, needed for terra ls, terra new,
terra learn). On Linux and Windows both land on your PATH. On
macOS the CLI lives inside the bundle, at
/Applications/Terra.app/Contents/MacOS/terra — the install script
symlinks it into /usr/local/bin; if you installed by dragging the
.dmg, link it yourself:

ln -sf /Applications/Terra.app/Contents/MacOS/terra /usr/local/bin/terra

v1.0.3

What's Changed

• release: v1.0.3 — pre-sign the bundled CLI (fixes the macOS signing failure) by @thewh1teagle in #29

Full Changelog: v1.0.2...v1.0.3

Platform support

macOS — tested. This is terra's development and v1 target. The
.dmg and the .app inside it are ad-hoc signed, not notarised, so
Gatekeeper shows the unidentified-developer prompt on first launch:
right-click the app and choose Open.

Linux (x86_64) and Windows (x86_64) — build-verified only. The
installers (.deb, -setup.exe) compile, pass the test suite and
pass clippy in CI, but the GUI has had far less real-world use than
on macOS. Bug reports welcome. The Windows installer is unsigned, so
SmartScreen will warn on first run — choose "More info" → "Run
anyway".

Every installer puts both halves of terra in place: terra-app (the
GUI) and terra (the CLI, needed for terra ls, terra new,
terra learn). On Linux and Windows both land on your PATH. On
macOS the CLI lives inside the bundle, at
/Applications/Terra.app/Contents/MacOS/terra — the install script
symlinks it into /usr/local/bin; if you installed by dragging the
.dmg, link it yourself:

ln -sf /Applications/Terra.app/Contents/MacOS/terra /usr/local/bin/terra

v1.0.2

release: v1.0.2 — installers only, packager-native signing, CLI in th…