chore(deps): termlens 0.11.2, and the report action with it - #108
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. Of the behaviour that arrives, what this repository can see: the pending-wrap cursor is reported on the last cell rather than one column past it (#401), so a screen whose last row filled now renders a header `Screen::parse` accepts; `unsupported()` reports the set forms of OSC 4/10/11 and the xterm title stack and spells a parameterless sequence `^[[s` rather than `^[[0s`; and `decode()` refuses a kitty transmission that names a file or a shared-memory object instead of decoding the name as pixels — this repository decodes its own cells, so the refusal is a guard it never reaches. The one `unsupported()` call site does not name a changed shape. The `report@` pin moves from v0.11.0 to v0.11.2. The action installs the latest termlens-cli either way; the pin is the action's own script, which gained `render --out` in v0.11.1 so a failed render no longer leaves a truncated file in the step summary. Verified with what CI runs: the full suite, `--test art_cli`, `--lib`, and `--test cli -- --ignored` (the termlens-cli suite a local `cargo test` skips). fmt and clippy clean. Signed-off-by: Vyncint Ng <115854244+vyncint@users.noreply.github.com>
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.Behaviour that arrives, of what this repository can observe: the pending-wrap cursor moves off
col == cols(#401),unsupported()gains the OSC 4/10/11 sets and the title stack and re-spells^[[0sas^[[s(#392–#394),decode()refuses indirect kitty transmissions rather than decoding a path as pixels (#402). The singleunsupported()call site here names none of the changed shapes.Checked with exactly what CI runs:
cargo test --all-features,--test art_cli,--lib, and--test cli -- --ignored— 4/4, 52, 119 and the full suite green. fmt and clippy clean.Unrelated, for the record:
tests/smoke.rs::years_users_and_errorsfails in my sandbox, but it fails identically onmainwith 0.11.0 (ran it twice on each), and it is#[ignore = "requires gh and network access"]in a target CI never runs with--ignored. Not this change, and not something this PR touches.