Repository navigation
chore(deps): termlens 0.11.7, and the report action with it - #184
Merged
Merged
Conversation
Locked at 0.11.4. 0.11.7 is a patch, so the `"0.11"` requirement in both manifests is unchanged; only the lock moves: termlens, and vt100 0.16.2 -> 0.18.1, the emulator underneath it. Of what arrives, nothing here needs a change. The 0.11.3 trailer split (termlens#374) and the styles block a piped `inspect` writes (#454, #478) were absorbed at the 0.11.4 bump. The emulator change (xterm-style resize, VS16 two columns wide, HVP/HPA/REP/ED 3 handled) reaches no assertion: the three exact `unsupported()` pins stay `^[[59m` alone, the checked-in goldens match unchanged, and the scrollback reads in `check_render.rs` and `triage_cli.rs` still hold. None of them reads history after an alternate-screen trip, which 0.11.7 stops duplicating (termlens#576). The three `report@` pins move from v0.11.4 to v0.11.7 (ff50ffc, checked with `gh api`). The action now writes its summary when `find` meets an unreadable directory (termlens#597). No screen snapshot here is an insta `.snap`, so its `INSTA_UPDATE: new` advice does not apply. The vendored skill is recopied from v0.11.7; it was still the v0.11.0 text, and AGENTS.md has a bump move the skill with it. Verified: `just ci`, and `cargo test -p reconverge-tui --test cli -- --ignored` against the published termlens-cli 0.11.7. Signed-off-by: Vyncint Ng <115854244+vyncint@users.noreply.github.com>
Picks up the rust-toolchain repin, which the zizmor gate needs. 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
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.
Locked at 0.11.4. 0.11.7 is a patch, so the
"0.11"requirement in bothmanifests is unchanged; only the lock moves: termlens, and vt100 0.16.2 ->
0.18.1, the emulator underneath it.
Of what arrives, nothing here needs a change. The 0.11.3 trailer split
(termlens#374) and the styles block a piped
inspectwrites (#454, #478)were absorbed at the 0.11.4 bump. The emulator change (xterm-style resize,
VS16 two columns wide, HVP/HPA/REP/ED 3 handled) reaches no assertion: the
three exact
unsupported()pins stay^[[59malone, the checked-ingoldens match unchanged, and the scrollback reads in
check_render.rsandtriage_cli.rsstill hold. None of them reads history after analternate-screen trip, which 0.11.7 stops duplicating (termlens#576).
The three
report@pins move from v0.11.4 to v0.11.7 (ff50ffc, checkedwith
gh api). The action now writes its summary whenfindmeets anunreadable directory (termlens#597). No screen snapshot here is an insta
.snap, so itsINSTA_UPDATE: newadvice does not apply. The vendoredskill is recopied from v0.11.7; it was still the v0.11.0 text, and
AGENTS.md has a bump move the skill with it.
Verified:
just ci, andcargo test -p reconverge-tui --test cli -- --ignoredagainst the published termlens-cli 0.11.7.The stress workflow is dispatched on this branch, because the emulator under every PTY test changed.
Signed-off-by: Vyncint Ng 115854244+vyncint@users.noreply.github.com