Skip to content

Bump tamboui.version from 0.6.0 to 0.7.0 - #780

Merged
github-actions[bot] merged 1 commit into
masterfrom
dependabot/maven/tamboui.version-0.7.0
Nov 16, 2026
Merged

github-actions[bot] merged 1 commit into
masterfrom
dependabot/maven/tamboui.version-0.7.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Contributor

Bumps tamboui.version from 0.6.0 to 0.7.0.
Updates dev.tamboui:tamboui-core from 0.6.0 to 0.7.0

Release notes

Sourced from dev.tamboui:tamboui-core's releases.

Release v0.7.0

The one with Keyboards

A big challenge with TUI applications is that keyboard events can be hard to handle uniformly and until recently getting info about modifier keys (think alt,ctrl,shift,command,hyper etc.) reliably was almost to truly impossible. Luckily Kitty Keyboard Protocol started being supported by all modern emulators and with version 0.7 TamboUI supports it too.

By default we run in AUTO mode which should work everywhere as it tries to enable Kitty Keyboard protocol but if termianl does not support it the emulator should be ignoring the activations. Meaning in case of error/incompatiblity it just falls back to legacy mode.

If the terminal emulator supports Kitty Keyboard Protocol you will have modifier information and can have code like this in your event handlers:

var m = event.modifiers();
if (m.ctrl() && m.superKey()) { // something when ctrl and super is active }

In .LEGACY and .AUTO mode you only get key presses but if you also want releases (great for games or UI's where you want full control over what happens based on keyboard) you can enable FULL mode:

TuiConfig.builder()
  .keyboardProtocol(KeyboardProtocol.FULL).
  .build();

We also updated most examples and docs to use semantic key predicates rather than access the raw keycodes - this should make editing and hotkey experience more uniform.

Talking about uniformity we also made the loading of keybindings deterministic so last one overrides and we will load a <binding>-<osname>.properties when you load a <binding>. That allows us to define common for all OS's keybindings for actions but when there are differences (like Mac using cmd rather than ctrl as used on Linux and Windows) you and users can have their platforms default meaning.

Give it a try and let us know if works for you !

Related RPs/issues:

  • Kitty Keyboard Protocol support — rich key events with proper modifiers and sensible defaults (#446/#592), plus runtime detection of whether the terminal honors it (#610)
  • Semantic key predicates everywhere — new KeyEvent.isTyping() + TextEditing; text widgets are now driven by semantic predicates instead of raw codes (#600/#612)
  • Word-wise editing — Ctrl+Left/Right to move, Ctrl+Backspace/Delete to delete by word (#616)
  • Hardened input decoding: ESC-prefix Alt keys, modifyOtherKeys, legacy Alt+control (#611); mis-decoded key/mouse sequences (#517); duplicate handler firing on one keypress (#481)
  • Visual event inspector + ASCII mouse device (#448/#585)

Mouse support for recording

In previous release we made the recorder feature accessible via API. The recorder feature allow you to write .tape files that defines keyboard input to drive a demo to then be saved as ascii animations. We use it to drive the widgets demo/animations, but you can use it too for your own apps.

In 0.7 we added mouse support to express scroll up/down, drag and mouse/trackpad clicks.

# Clicks - "Command × y"
Click 10 5 # left click at column 10 row 5
RightClick 10 5 
MiddleClick 10 5
# Press / release separately (e.g. hold while something else
happens )
MouseDown 10 5
</tr></table> 

... (truncated)

Commits
  • 6a8c513 [release] Releasing version 0.7.0
  • b691282 fix: action handler missing layout
  • 457833d docs(chart): clarify out-of-range and missing-point behaviour (#630)
  • 0b3a4ed perf: fast path and linear constraints for Layout.split (#559) (#560)
  • 452397b fix: layout spacing taken out twice, and Fill(0) breaking the solver (#468)
  • 6317073 fix: a chart point far outside the axis bounds can hang rendering or draw a s...
  • b7b111a fix: text() with \n renders each line on its own row (#469)
  • f316a61 fix: one key press runs a toolkit element's key handler several times (#481)
  • dd9b7fb fix: q quits with the emacs, IntelliJ and VS Code bindings, and a bindings fi...
  • 3046c90 refactor(bindings): make platform binding overlays OS-generic, not macOS-only...
  • Additional commits viewable in compare view

Updates dev.tamboui:tamboui-widgets from 0.6.0 to 0.7.0

Release notes

Sourced from dev.tamboui:tamboui-widgets's releases.

Release v0.7.0

The one with Keyboards

A big challenge with TUI applications is that keyboard events can be hard to handle uniformly and until recently getting info about modifier keys (think alt,ctrl,shift,command,hyper etc.) reliably was almost to truly impossible. Luckily Kitty Keyboard Protocol started being supported by all modern emulators and with version 0.7 TamboUI supports it too.

By default we run in AUTO mode which should work everywhere as it tries to enable Kitty Keyboard protocol but if termianl does not support it the emulator should be ignoring the activations. Meaning in case of error/incompatiblity it just falls back to legacy mode.

If the terminal emulator supports Kitty Keyboard Protocol you will have modifier information and can have code like this in your event handlers:

var m = event.modifiers();
if (m.ctrl() && m.superKey()) { // something when ctrl and super is active }

In .LEGACY and .AUTO mode you only get key presses but if you also want releases (great for games or UI's where you want full control over what happens based on keyboard) you can enable FULL mode:

TuiConfig.builder()
  .keyboardProtocol(KeyboardProtocol.FULL).
  .build();

We also updated most examples and docs to use semantic key predicates rather than access the raw keycodes - this should make editing and hotkey experience more uniform.

Talking about uniformity we also made the loading of keybindings deterministic so last one overrides and we will load a <binding>-<osname>.properties when you load a <binding>. That allows us to define common for all OS's keybindings for actions but when there are differences (like Mac using cmd rather than ctrl as used on Linux and Windows) you and users can have their platforms default meaning.

Give it a try and let us know if works for you !

Related RPs/issues:

  • Kitty Keyboard Protocol support — rich key events with proper modifiers and sensible defaults (#446/#592), plus runtime detection of whether the terminal honors it (#610)
  • Semantic key predicates everywhere — new KeyEvent.isTyping() + TextEditing; text widgets are now driven by semantic predicates instead of raw codes (#600/#612)
  • Word-wise editing — Ctrl+Left/Right to move, Ctrl+Backspace/Delete to delete by word (#616)
  • Hardened input decoding: ESC-prefix Alt keys, modifyOtherKeys, legacy Alt+control (#611); mis-decoded key/mouse sequences (#517); duplicate handler firing on one keypress (#481)
  • Visual event inspector + ASCII mouse device (#448/#585)

Mouse support for recording

In previous release we made the recorder feature accessible via API. The recorder feature allow you to write .tape files that defines keyboard input to drive a demo to then be saved as ascii animations. We use it to drive the widgets demo/animations, but you can use it too for your own apps.

In 0.7 we added mouse support to express scroll up/down, drag and mouse/trackpad clicks.

# Clicks - "Command × y"
Click 10 5 # left click at column 10 row 5
RightClick 10 5 
MiddleClick 10 5
# Press / release separately (e.g. hold while something else
happens )
MouseDown 10 5
</tr></table> 

... (truncated)

Commits
  • 6a8c513 [release] Releasing version 0.7.0
  • b691282 fix: action handler missing layout
  • 457833d docs(chart): clarify out-of-range and missing-point behaviour (#630)
  • 0b3a4ed perf: fast path and linear constraints for Layout.split (#559) (#560)
  • 452397b fix: layout spacing taken out twice, and Fill(0) breaking the solver (#468)
  • 6317073 fix: a chart point far outside the axis bounds can hang rendering or draw a s...
  • b7b111a fix: text() with \n renders each line on its own row (#469)
  • f316a61 fix: one key press runs a toolkit element's key handler several times (#481)
  • dd9b7fb fix: q quits with the emacs, IntelliJ and VS Code bindings, and a bindings fi...
  • 3046c90 refactor(bindings): make platform binding overlays OS-generic, not macOS-only...
  • Additional commits viewable in compare view

Updates dev.tamboui:tamboui-tui from 0.6.0 to 0.7.0

Release notes

Sourced from dev.tamboui:tamboui-tui's releases.

Release v0.7.0

The one with Keyboards

A big challenge with TUI applications is that keyboard events can be hard to handle uniformly and until recently getting info about modifier keys (think alt,ctrl,shift,command,hyper etc.) reliably was almost to truly impossible. Luckily Kitty Keyboard Protocol started being supported by all modern emulators and with version 0.7 TamboUI supports it too.

By default we run in AUTO mode which should work everywhere as it tries to enable Kitty Keyboard protocol but if termianl does not support it the emulator should be ignoring the activations. Meaning in case of error/incompatiblity it just falls back to legacy mode.

If the terminal emulator supports Kitty Keyboard Protocol you will have modifier information and can have code like this in your event handlers:

var m = event.modifiers();
if (m.ctrl() && m.superKey()) { // something when ctrl and super is active }

In .LEGACY and .AUTO mode you only get key presses but if you also want releases (great for games or UI's where you want full control over what happens based on keyboard) you can enable FULL mode:

TuiConfig.builder()
  .keyboardProtocol(KeyboardProtocol.FULL).
  .build();

We also updated most examples and docs to use semantic key predicates rather than access the raw keycodes - this should make editing and hotkey experience more uniform.

Talking about uniformity we also made the loading of keybindings deterministic so last one overrides and we will load a <binding>-<osname>.properties when you load a <binding>. That allows us to define common for all OS's keybindings for actions but when there are differences (like Mac using cmd rather than ctrl as used on Linux and Windows) you and users can have their platforms default meaning.

Give it a try and let us know if works for you !

Related RPs/issues:

  • Kitty Keyboard Protocol support — rich key events with proper modifiers and sensible defaults (#446/#592), plus runtime detection of whether the terminal honors it (#610)
  • Semantic key predicates everywhere — new KeyEvent.isTyping() + TextEditing; text widgets are now driven by semantic predicates instead of raw codes (#600/#612)
  • Word-wise editing — Ctrl+Left/Right to move, Ctrl+Backspace/Delete to delete by word (#616)
  • Hardened input decoding: ESC-prefix Alt keys, modifyOtherKeys, legacy Alt+control (#611); mis-decoded key/mouse sequences (#517); duplicate handler firing on one keypress (#481)
  • Visual event inspector + ASCII mouse device (#448/#585)

Mouse support for recording

In previous release we made the recorder feature accessible via API. The recorder feature allow you to write .tape files that defines keyboard input to drive a demo to then be saved as ascii animations. We use it to drive the widgets demo/animations, but you can use it too for your own apps.

In 0.7 we added mouse support to express scroll up/down, drag and mouse/trackpad clicks.

# Clicks - "Command × y"
Click 10 5 # left click at column 10 row 5
RightClick 10 5 
MiddleClick 10 5
# Press / release separately (e.g. hold while something else
happens )
MouseDown 10 5
</tr></table> 

... (truncated)

Commits
  • 6a8c513 [release] Releasing version 0.7.0
  • b691282 fix: action handler missing layout
  • 457833d docs(chart): clarify out-of-range and missing-point behaviour (#630)
  • 0b3a4ed perf: fast path and linear constraints for Layout.split (#559) (#560)
  • 452397b fix: layout spacing taken out twice, and Fill(0) breaking the solver (#468)
  • 6317073 fix: a chart point far outside the axis bounds can hang rendering or draw a s...
  • b7b111a fix: text() with \n renders each line on its own row (#469)
  • f316a61 fix: one key press runs a toolkit element's key handler several times (#481)
  • dd9b7fb fix: q quits with the emacs, IntelliJ and VS Code bindings, and a bindings fi...
  • 3046c90 refactor(bindings): make platform binding overlays OS-generic, not macOS-only...
  • Additional commits viewable in compare view

Updates dev.tamboui:tamboui-toolkit from 0.6.0 to 0.7.0

Release notes

Sourced from dev.tamboui:tamboui-toolkit's releases.

Release v0.7.0

The one with Keyboards

A big challenge with TUI applications is that keyboard events can be hard to handle uniformly and until recently getting info about modifier keys (think alt,ctrl,shift,command,hyper etc.) reliably was almost to truly impossible. Luckily Kitty Keyboard Protocol started being supported by all modern emulators and with version 0.7 TamboUI supports it too.

By default we run in AUTO mode which should work everywhere as it tries to enable Kitty Keyboard protocol but if termianl does not support it the emulator should be ignoring the activations. Meaning in case of error/incompatiblity it just falls back to legacy mode.

If the terminal emulator supports Kitty Keyboard Protocol you will have modifier information and can have code like this in your event handlers:

var m = event.modifiers();
if (m.ctrl() && m.superKey()) { // something when ctrl and super is active }

In .LEGACY and .AUTO mode you only get key presses but if you also want releases (great for games or UI's where you want full control over what happens based on keyboard) you can enable FULL mode:

TuiConfig.builder()
  .keyboardProtocol(KeyboardProtocol.FULL).
  .build();

We also updated most examples and docs to use semantic key predicates rather than access the raw keycodes - this should make editing and hotkey experience more uniform.

Talking about uniformity we also made the loading of keybindings deterministic so last one overrides and we will load a <binding>-<osname>.properties when you load a <binding>. That allows us to define common for all OS's keybindings for actions but when there are differences (like Mac using cmd rather than ctrl as used on Linux and Windows) you and users can have their platforms default meaning.

Give it a try and let us know if works for you !

Related RPs/issues:

  • Kitty Keyboard Protocol support — rich key events with proper modifiers and sensible defaults (#446/#592), plus runtime detection of whether the terminal honors it (#610)
  • Semantic key predicates everywhere — new KeyEvent.isTyping() + TextEditing; text widgets are now driven by semantic predicates instead of raw codes (#600/#612)
  • Word-wise editing — Ctrl+Left/Right to move, Ctrl+Backspace/Delete to delete by word (#616)
  • Hardened input decoding: ESC-prefix Alt keys, modifyOtherKeys, legacy Alt+control (#611); mis-decoded key/mouse sequences (#517); duplicate handler firing on one keypress (#481)
  • Visual event inspector + ASCII mouse device (#448/#585)

Mouse support for recording

In previous release we made the recorder feature accessible via API. The recorder feature allow you to write .tape files that defines keyboard input to drive a demo to then be saved as ascii animations. We use it to drive the widgets demo/animations, but you can use it too for your own apps.

In 0.7 we added mouse support to express scroll up/down, drag and mouse/trackpad clicks.

# Clicks - "Command × y"
Click 10 5 # left click at column 10 row 5
RightClick 10 5 
MiddleClick 10 5
# Press / release separately (e.g. hold while something else
happens )
MouseDown 10 5
</tr></table> 

... (truncated)

Commits
  • 6a8c513 [release] Releasing version 0.7.0
  • b691282 fix: action handler missing layout
  • 457833d docs(chart): clarify out-of-range and missing-point behaviour (#630)
  • 0b3a4ed perf: fast path and linear constraints for Layout.split (#559) (#560)
  • 452397b fix: layout spacing taken out twice, and Fill(0) breaking the solver (#468)
  • 6317073 fix: a chart point far outside the axis bounds can hang rendering or draw a s...
  • b7b111a fix: text() with \n renders each line on its own row (#469)
  • f316a61 fix: one key press runs a toolkit element's key handler several times (#481)
  • dd9b7fb fix: q quits with the emacs, IntelliJ and VS Code bindings, and a bindings fi...
  • 3046c90 refactor(bindings): make platform binding overlays OS-generic, not macOS-only...
  • Additional commits viewable in compare view

Updates dev.tamboui:tamboui-aesh-backend from 0.6.0 to 0.7.0

Release notes

Sourced from dev.tamboui:tamboui-aesh-backend's releases.

Release v0.7.0

The one with Keyboards

A big challenge with TUI applications is that keyboard events can be hard to handle uniformly and until recently getting info about modifier keys (think alt,ctrl,shift,command,hyper etc.) reliably was almost to truly impossible. Luckily Kitty Keyboard Protocol started being supported by all modern emulators and with version 0.7 TamboUI supports it too.

By default we run in AUTO mode which should work everywhere as it tries to enable Kitty Keyboard protocol but if termianl does not support it the emulator should be ignoring the activations. Meaning in case of error/incompatiblity it just falls back to legacy mode.

If the terminal emulator supports Kitty Keyboard Protocol you will have modifier information and can have code like this in your event handlers:

var m = event.modifiers();
if (m.ctrl() && m.superKey()) { // something when ctrl and super is active }

In .LEGACY and .AUTO mode you only get key presses but if you also want releases (great for games or UI's where you want full control over what happens based on keyboard) you can enable FULL mode:

TuiConfig.builder()
  .keyboardProtocol(KeyboardProtocol.FULL).
  .build();

We also updated most examples and docs to use semantic key predicates rather than access the raw keycodes - this should make editing and hotkey experience more uniform.

Talking about uniformity we also made the loading of keybindings deterministic so last one overrides and we will load a <binding>-<osname>.properties when you load a <binding>. That allows us to define common for all OS's keybindings for actions but when there are differences (like Mac using cmd rather than ctrl as used on Linux and Windows) you and users can have their platforms default meaning.

Give it a try and let us know if works for you !

Related RPs/issues:

  • Kitty Keyboard Protocol support — rich key events with proper modifiers and sensible defaults (#446/#592), plus runtime detection of whether the terminal honors it (#610)
  • Semantic key predicates everywhere — new KeyEvent.isTyping() + TextEditing; text widgets are now driven by semantic predicates instead of raw codes (#600/#612)
  • Word-wise editing — Ctrl+Left/Right to move, Ctrl+Backspace/Delete to delete by word (#616)
  • Hardened input decoding: ESC-prefix Alt keys, modifyOtherKeys, legacy Alt+control (#611); mis-decoded key/mouse sequences (#517); duplicate handler firing on one keypress (#481)
  • Visual event inspector + ASCII mouse device (#448/#585)

Mouse support for recording

In previous release we made the recorder feature accessible via API. The recorder feature allow you to write .tape files that defines keyboard input to drive a demo to then be saved as ascii animations. We use it to drive the widgets demo/animations, but you can use it too for your own apps.

In 0.7 we added mouse support to express scroll up/down, drag and mouse/trackpad clicks.

# Clicks - "Command × y"
Click 10 5 # left click at column 10 row 5
RightClick 10 5 
MiddleClick 10 5
# Press / release separately (e.g. hold while something else
happens )
MouseDown 10 5
</tr></table> 

... (truncated)

Commits
  • 6a8c513 [release] Releasing version 0.7.0
  • b691282 fix: action handler missing layout
  • 457833d docs(chart): clarify out-of-range and missing-point behaviour (#630)
  • 0b3a4ed perf: fast path and linear constraints for Layout.split (#559) (#560)
  • 452397b fix: layout spacing taken out twice, and Fill(0) breaking the solver (#468)
  • 6317073 fix: a chart point far outside the axis bounds can hang rendering or draw a s...
  • b7b111a fix: text() with \n renders each line on its own row (#469)
  • f316a61 fix: one key press runs a toolkit element's key handler several times (#481)
  • dd9b7fb fix: q quits with the emacs, IntelliJ and VS Code bindings, and a bindings fi...
  • 3046c90 refactor(bindings): make platform binding overlays OS-generic, not macOS-only...
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps `tamboui.version` from 0.6.0 to 0.7.0.

Updates `dev.tamboui:tamboui-core` from 0.6.0 to 0.7.0
- [Release notes](https://github.com/tamboui/tamboui/releases)
- [Commits](tamboui/tamboui@v0.6.0...v0.7.0)

Updates `dev.tamboui:tamboui-widgets` from 0.6.0 to 0.7.0
- [Release notes](https://github.com/tamboui/tamboui/releases)
- [Commits](tamboui/tamboui@v0.6.0...v0.7.0)

Updates `dev.tamboui:tamboui-tui` from 0.6.0 to 0.7.0
- [Release notes](https://github.com/tamboui/tamboui/releases)
- [Commits](tamboui/tamboui@v0.6.0...v0.7.0)

Updates `dev.tamboui:tamboui-toolkit` from 0.6.0 to 0.7.0
- [Release notes](https://github.com/tamboui/tamboui/releases)
- [Commits](tamboui/tamboui@v0.6.0...v0.7.0)

Updates `dev.tamboui:tamboui-aesh-backend` from 0.6.0 to 0.7.0
- [Release notes](https://github.com/tamboui/tamboui/releases)
- [Commits](tamboui/tamboui@v0.6.0...v0.7.0)

---
updated-dependencies:
- dependency-name: dev.tamboui:tamboui-core
  dependency-version: 0.7.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: dev.tamboui:tamboui-widgets
  dependency-version: 0.7.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: dev.tamboui:tamboui-tui
  dependency-version: 0.7.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: dev.tamboui:tamboui-toolkit
  dependency-version: 0.7.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: dev.tamboui:tamboui-aesh-backend
  dependency-version: 0.7.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file java Pull requests that update java code labels Nov 16, 2026
@github-actions
github-actions Bot merged commit ab542cb into master Nov 16, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file java Pull requests that update java code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants