chore(deps): termlens 0.11.2, and the report action with it - #52
Merged
Merged
Conversation
Locked at 0.11.0 since the 09-11 migration, two releases behind. Both are patches, so the `"0.11"` requirement is unchanged and only the lock moves; `check-skill-version.sh` compares major.minor, so the vendored skill copy stays as it is. The two `Screen::unsupported()` assertions were the ones to watch. 0.11.2 makes that record report more — the set forms of OSC 4/10/11 (#392) and the xterm title stack (#393) — and re-spells a parameterless sequence `^[[s` rather than `^[[0s` (#394), and both sites compare the view against an exact slice, which is equal only when the retained shapes match and nothing overflowed. Both still hold: the TUI emits neither family, and `^[[59m` carries a parameter so the re-spelling does not reach it. Also arriving: the pending-wrap cursor is reported on the last cell rather than one column past it (#401), so a screen whose last row filled renders a header `Screen::parse` accepts, and the JSON reader no longer refuses a screen the text parser would take. The three `report@` pins move from v0.11.0 to v0.11.2. Nothing here pins `cli-version`, so the action installs the version the lockfile names and the renderer stays one release with the harness. Verified: `cargo test --workspace --locked` (36 result lines, 0 failures), `cargo test -p oxidelake-tui --test termlens_cli --locked -- --ignored` against an installed termlens-cli 0.11.2 — the suite a plain `cargo test` skips and CI asks for by name — plus fmt, clippy and check-skill-version.sh. Signed-off-by: Vyncint Ng <115854244+vyncint@users.noreply.github.com>
vyncint
force-pushed
the
chore/termlens-0.11.2
branch
from
September 19, 2026 13:48
ed25de5 to
2ae16be
Compare
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
1 participant
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.
Two releases behind since the 09-11 migration. Both patches, so
"0.11"is unchanged and onlyCargo.lockmoves;check-skill-version.shcompares major.minor, so the vendored skill copy stays.The two
Screen::unsupported()assertions were the risk. 0.11.2 adds shapes to that record (OSC 4/10/11 sets, the xterm title stack) and re-spells^[[0sas^[[s, and both sites compare the view against an exact slice — equal only when the retained shapes match and nothing overflowed. Both hold: the TUI emits neither family, and^[[59mcarries a parameter so the re-spelling does not reach it.Also arriving: the pending-wrap cursor moves off
col == cols(#401).Checked:
cargo test --workspace --locked(36 result lines, 0 failures),cargo test -p oxidelake-tui --test termlens_cli --locked -- --ignored(4/4) against an installed termlens-cli 0.11.2 — the suite a localcargo testskips and CI runs by name — plus fmt, clippy andcheck-skill-version.sh.Three
report@pins move to v0.11.2. Nothing here pinscli-version, so the action installs what the lockfile names.