Repository navigation
Conversation
why: The libtmux ports, MCP servers and workspace builders now support tmux 3.3a and newer, judged by the connected daemon. Pages, example prerequisites and port install notes still said 3.2 or 3.2a, so a reader on 3.2a would follow instructions the libraries refuse. what: - Move every "tmux 3.2 or newer" and "3.2a or newer" statement in the shared and per-port content to 3.3a, including the JVM "3.2a through 3.7c" range and Ruby's "3.3 or newer" so 3.3 no longer reads as supported - Update the generated example introductions, home quickstart prerequisites and the Julia install note to the same floor - State on each workspace compatibility page and the MCP entry pages that a daemon older than 3.3a is refused before any effect - Add a tmux support guide that gives the version rules and links from the guides index - Leave historical records alone: manual archives for 3.2a, example runs on 3.2a and 3.7c, and tmux facts such as the 3.2 hook origin Port guides and API data under site/src/data come from pinned port revisions and change when those ports publish their own floor. Verified: gen-mentions output is unchanged; test results follow.
why: Scattered "tmux X or newer" statements across content, example prerequisites and install notes had no check, so a page could keep an old floor after the support contract moved. what: - Scan the content, home quickstart data, port install notes and example introductions for "tmux X or newer", "tmux X+" and "tmux X through Y" and require X to be 3.3a - Skip facts about tmux itself, which follow "on", and staged port guides, which carry the pinned port's own floor - Reword the legacy 88-colour flag note so it states a tmux fact and not a minimum Verified: the check passes; restoring one "tmux 3.2a or newer" line in topics/traversal.md makes it fail naming that file, and restoring the line makes it pass.
tony
force-pushed
the
bump-min-tmux-000
branch
from
October 17, 2026 13:38
2a58002 to
99df2a3
Compare
why: The assembled-site link check failed on PR #150 with 11 broken links. Port pages linked `/guides/tmux-support/`, which resolves inside each port's own docs (`/en/<port>/latest/guides/tmux-support/`), and no port has its own copy of that guide. Shared guides are served under `/en/tmux/guides/`, which existing port pages reach by relative path. what: - Point the workspace compatibility pages at `../../../../../tmux/guides/tmux-support/` - Point the Python, Go and Rust MCP entry pages at `../../../tmux/guides/tmux-support/`
tony
added a commit
that referenced
this pull request
Oct 17, 2026
why: The assembled-site link check failed on PR #150 with 11 broken links. Port pages linked `/guides/tmux-support/`, which resolves inside each port's own docs (`/en/<port>/latest/guides/tmux-support/`), and no port has its own copy of that guide. Shared guides are served under `/en/tmux/guides/`, which existing port pages reach by relative path. what: - Point the workspace compatibility pages at `../../../../../tmux/guides/tmux-support/` - Point the Python, Go and Rust MCP entry pages at `../../../tmux/guides/tmux-support/`
tony
added a commit
that referenced
this pull request
Oct 17, 2026
why: The assembled-site link check failed on PR #150 with 11 broken links. Port pages linked `/guides/tmux-support/`, which resolves inside each port's own docs (`/en/<port>/latest/guides/tmux-support/`), and no port has its own copy of that guide. Shared guides are served under `/en/tmux/guides/`, which existing port pages reach by relative path. what: - Point the workspace compatibility pages at `../../../../../tmux/guides/tmux-support/` - Point the Python, Go and Rust MCP entry pages at `../../../tmux/guides/tmux-support/`
tony
force-pushed
the
bump-min-tmux-000
branch
2 times, most recently
from
October 17, 2026 18:53
7a7a677 to
4d5d622
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Move every page, example prerequisite and install note that states a tmux minimum to 3.3a, and add a tmux support guide that states the version rules. The libraries judge the connected daemon, compare patch letters (3.3 is below 3.3a), and refuse an older daemon before the requested operation has any effect.
guides/tmux-supportpage covers daemon versus client version checks, absent endpoints, replacement daemons, raw commands, batches, MCP and workspace entry points, the standalone-Vand-hdiagnostics, and the built-in command assumption.site/test/tmux-minimum.test.ts) requires every "tmux X or newer", "tmux X+" and "tmux X through Y" statement to name 3.3a.site/src/data. Those come from pinned port revisions and change when each port publishes its own floor.Validation (Node 26.5.1, pnpm 12.7.0, local;
pnpm test:mediumwas not usable because its ten-second budget was exceeded on a loaded host, so its components ran separately):pnpm run type-checkreports zero errors.pnpm run --recursive lintandoxlint scriptsreport only existing warnings.check-api-links,check-nav,gen-mentions --check(Ruby and Lua guides staged from source first),gen-shell-ports --checkandgen-brand-css --checkpass.topics/traversal.mdmakes the new check fail naming that file; restoring the fix passes (docs/deliberate-break-floor-gate.login the evidence folder).Not run: the assembled-site build and publication audit (
pnpm test:publication), which need the port checkouts and run in hosted CI.Closes #146.