GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — py(deps) Bump libtmux 0.56.0 by tony · Pull Request #1038 · tmux-python/tmuxp

Conversation

@tony

@tony tony commented May 10, 2026

Copy link
Copy Markdown
Member

Summary

  • Bump libtmux from ~=0.55.0 to ~=0.56.0
  • Whitelist libtmux from the exclude-newer cooldown so contributor uv sync works against the new pin without waiting 3 days
  • Picks up libtmux 0.55.1 (test-fixture socket-cleanup fix) and 0.56.0 (50+ new tmux command wrappers, move_window() auto-refresh fix, control_mode pytest fixture, TMUX_MAX_VERSION -> 3.7)
  • No tmuxp code or test changes needed — v0.56.0 is purely additive on the surface tmuxp imports, and tmuxp's only Window.move_window() call doesn't read post-move attributes so the upstream auto-refresh fix is a free correctness improvement

Upstream changes

libtmux 0.56.0 (2026-05-10)

What's new (#653)

  • Interactive tmux commands now scriptable: new wrappers for the commands that previously required hand-rolled Server.cmd() calls — Pane.display_popup, Server.display_menu, Server.command_prompt, Server.confirm_before, Session.detach_client, Server.detach_client, Server.detach_all_clients, Pane.display_panes, plus the choose_* family (choose_buffer, choose_client, choose_tree). The three detach-client wrappers each map to one tmux flag group with a single subprocess call.
  • tmux buffer I/O suite: Server.set_buffer, show_buffer, delete_buffer, save_buffer, load_buffer, list_buffers, plus Pane.paste_buffer round-trip pane content through named tmux buffers.
  • Key bindings and shell execution: Server gains bind_key, unbind_key, list_keys, list_commands, run_shell, if_shell, source_file, list_clients, start_server, lock_server, lock_client, refresh_client, suspend_client, server_access, show_messages, show_prompt_history, clear_prompt_history. Session gains lock_session. Pane gains send_prefix.
  • Window/pane manipulation parity: new Window.swap, link, unlink, respawn, last_pane, next_layout, previous_layout, rotate; new Pane.swap, join, break_pane, move, pipe, clear_history, respawn, copy_mode, clock_mode, customize_mode, find_window; new Server.wait_for, Session.last_window, next_window, previous_window.
  • Filled-in flag coverage on existing methods: Pane.send_keys (literal, hex, key-name, format, client), Pane.split (percentage=), Pane.capture_pane (alternate-screen, quiet, write-to-buffer), Pane.display_message, Pane.display_popup (target_client=, -c), Window.move_window (after, before, kill, renumber), Window.select_layout (spread, next, previous), Server.new_session, Session.new_window, Server.set_environment, Server.show_options (quiet=).
  • control_mode pytest fixture: spawns a real tmux -C client attached to the session so commands that require an attached client are testable without a TTY.

Bug fixes (#653)

  • Window.move_window() now refreshes the moved window automatically; previously the Window object pointed at its pre-move index until a manual refresh(). tmuxp's only call site (workspace/builder.py:629) doesn't read post-move attributes, so this is a free correctness improvement.

Development (#653)

  • TMUX_MAX_VERSION bumped to "3.7", unlocking method coverage already version-gated for tmux 3.7 (notably command_prompt(bspace_exit=) and show_messages(terminals=, jobs=)). No effect on installations running tmux 3.6 or earlier.

libtmux 0.55.1 (2026-04-19)

  • pytest_plugin: server and TestServer fixture finalizers now unlink(2) the tmux socket from /tmp/tmux-<uid>/ in addition to server.kill(). tmux doesn't reliably unlink its socket on non-graceful exit, so long-lived dev machines were accumulating 10k+ stale libtmux_test* entries (Remove Python 2.7 #661, fixes Freeze config for attached session #660).

Changes in this PR

  • Whitelist commit (1d6bb889): adds libtmux = false to [tool.uv.exclude-newer-package] in pyproject.toml so the rolling 3-day cooldown doesn't block contributor uv sync against the new pin. Mirrors the precedent set in 6c0a0b2d for the gp-* dep surface.
  • Package bump (3754a060): pyproject.toml libtmux~=0.55.0 -> libtmux~=0.56.0; uv.lock regenerated via uv lock --upgrade-package libtmux (other packages unchanged).
  • No code changes: tmuxp imports only stable APIs unaffected by v0.56.0.
  • No test changes: existing test surface continues to work against the new wheel.

Test plan

  • uv run py.test passes locally
  • uv run mypy passes
  • uv run ruff check . passes
  • CI green on all matrix legs (CI doesn't carry the user-level cooldown so it won't need the whitelist to resolve)

Release: https://github.com/tmux-python/libtmux/releases/tag/v0.56.0
Changelog: https://libtmux.git-pull.com/history.html

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
tony added 2 commits May 10, 2026 08:52
@tony
py(deps[uv]) Whitelist libtmux from exclude-newer cooldown
1d6bb88
why: libtmux releases in lockstep with the tmuxp release cycle —
when libtmux 0.56.0 lands and tmuxp needs to bump, the rolling
exclude-newer = now − P3D window in the lockfile filters every
release younger than 3 days, so contributor `uv sync` against the
new pin would fail until the window naturally clears:

    × No solution found when resolving dependencies:
      ╰─▶ Because libtmux==0.56.0 was published after the exclude
          newer time and only libtmux<=0.55.1 is available...
      hint: Consider using `exclude-newer-package` to override the
      cutoff for this package.

libtmux is a git-pull package (same maintainer surface as gp-libs
and the gp-sphinx workspace already whitelisted in 6c0a0b2), so
the supply-chain cooldown adds friction without adding safety —
gp == git-pull, and so are we. Whitelisting now also unblocks the
imminent ~=0.55.0 -> ~=0.56.0 bump without staging it on a
3-day-delayed branch.

what:
- Add `libtmux = false` to [tool.uv.exclude-newer-package],
  slotted between the gp-* group and the sphinx-* group in line
  with the existing visual grouping. No comment churn — the
  existing block-level comment from 6c0a0b2 already covers the
  rationale (git-pull lockstep releases, vcspull/libvcs precedent).
@tony
py(deps) Bump libtmux 0.55.0 -> 0.56.0
3754a06
@codecov

codecov Bot commented May 10, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.96%. Comparing base (3f4d107) to head (9f48a47).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1038   +/-   ##
=======================================
  Coverage   81.96%   81.96%           
=======================================
  Files          28       28           
  Lines        2545     2545           
  Branches      485      485           
=======================================
  Hits         2086     2086           
  Misses        328      328           
  Partials      131      131           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@tony tony changed the title py(deps) Bump libtmux ~=0.55.0 -> ~=0.56.0 py(deps) Bump libtmux 0.56.0 May 10, 2026
@tony
tony force-pushed the libtmux-v0.56.0 branch from 54f123b to 8c4ef82 Compare May 10, 2026 14:37
@tony
docs(CHANGES) libtmux ~=0.55.0 -> ~=0.56.0
9f48a47
why: Document the libtmux dependency bump for the upcoming
release so an end user skimming next-version notes can confirm
their `tmuxp load`/`freeze`/YAML workflow won't change. The first
draft of this entry leaned on libtmux internals
(`control_mode` fixture, `TMUX_MAX_VERSION` ceiling, the
`move_window()` auto-refresh) — accurate but useless to a session-
manager user, who never meets those names.

what:
- Add a Breaking Changes entry under the unreleased tmuxp 1.68.0
  block. Frames the bump through the one tmuxp surface where users
  actually meet libtmux APIs (`tmuxp shell`): notes that 0.56.0
  broadens the tmux command coverage available there (interactive
  commands, buffer I/O, key bindings, window/pane manipulation),
  and that 0.55.1 is a test-fixture cleanup. Skips the upstream's
  contributor-only additions (pytest fixture, version-ceiling
  bump, etc.) — those belong in libtmux release notes, not the
  session-manager changelog.
- Heading style mirrors the prior 1.65.0 entry verbatim
  (`#### **libtmux** minimum bumped from ...`) so the changelog
  reads consistently across libtmux jumps.
@tony
tony force-pushed the libtmux-v0.56.0 branch from 8c4ef82 to 9f48a47 Compare May 10, 2026 14:38
@tony
tony merged commit c675892 into master May 10, 2026
13 checks passed

Uh oh!

There was an error while loading. Please reload this page.

@tony
tony deleted the libtmux-v0.56.0 branch May 10, 2026 14:47
@tony tony mentioned this pull request May 10, 2026
refactor(cli/load,tests) Migrate display-message to typed wrapper #1039
Open
6 tasks done
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

1 participant

@tony
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.