ci: pin the termlens report action to v0.11.0 - #107
Merged
Merged
Conversation
Missed by the dependency bump: that PR moved the requirement, the lockfile and the vendored skill, and this pin is the one place the *tool* version appears here. Left at v0.10.1 the action would install a 0.10 termlens-cli to render the screens of a suite running against 0.11 — which reads a saved screen slightly differently since termlens#340. The SHA is the v0.11.0 tag, verified with `gh api` rather than typed. 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.
Missed by #106. That PR moved the requirement, the lockfile and the vendored skill; this pin is the one place the tool version appears in this repository, and it stayed at
v0.10.1.Left as it was, a failing PTY job would install a 0.10
termlens-clito render the screens of a suite running against 0.11 — and since termlens#340 the two read a saved screen slightly differently, so the renderer would be a release behind the thing it is rendering. Only reachable on a failure, which is exactly when a confusing artifact costs the most.b8af0fa457dd023aa708a493b7f485256009f1a5is thev0.11.0tag, verified withgh apirather than typed. The four sibling repositories that carry this action were bumped in their own migration PRs; this is the one that slipped through, found by grepping every workflow in the family for the old SHA after the fact.