GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |
GeezerVison is showing github.com — Require coordinated optional tmux operation guards by tony · Pull Request #1093 · tmux-python/tmuxp Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@ ## bump-min-tmux-000 #1093 +/- ## ===================================================== + Coverage 82.44% 82.48% +0.03% ===================================================== Files 31 31 Lines 2826 2826 Branches 525 525 ===================================================== + Hits 2330 2331 +1 + Misses 357 356 -1 Partials 139 139 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
c01963c to
f3f2518
Compare
6d89492 to
bfab78b
Compare
f3f2518 to
357b145
Compare
bfab78b to
44da478
Compare
357b145 to
dc81900
Compare
why: Use the coordinated parent revision with layout refusal and
per-operation compatibility.
what:
- Pin the immutable policy-2 libtmux source in project and lock.
- Keep the matching 0.62 package metadata.
why: A package version can still lack required operation guards. what: - Require integer policy 2 before workspace imports or shell code. - Exercise refusal, supported operations and native layout behavior.
why: Ordinary workspace support and optional operation requirements
need separate installation and behavior guidance.
what:
- Describe operation floors and narrow layout refusal.
- Explain coordinated source installation and native client needs.
why: Existing custom code needs the individual tmux requirements. what: - Document optional operation guards and policy-2 installation. - Keep ordinary tmux 3.3a operations available.
why: The next release changes optional-operation version checks. what: - Record operation requirements and layout refusal behavior.
The backend gate compared TMUX_OPTIONAL_FEATURE_POLICY_VERSION, which libtmux no longer exposes. Require libtmux._internal.support.require_commands instead; a libtmux without it is refused before builders, plugins or shell code run, and the layout test now expects LibTmuxException on every release, because libtmux raises InvalidLayout (a LibTmuxException) from the 3.3a guard instead of a bare ValueError. Tests: a libtmux without require_commands is refused for builders, plugins and shell code with no effect. Dropping the name from the gate fails all three. The feature-policy and version check modules (30 cases) pass on 3.7d and 3.3a.
Replace the policy-version sentence with the require_commands requirement. Keep the migration note separate from runtime changes.
Replace the policy-version sentence with the require_commands requirement. Keep the release note separate from runtime changes.
44da478 to
177db45
Compare
dc81900 to
0520149
Compare
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.