docs: record the tmux regression fix in the 1.14.0 entry - #62
Merged
Merged
Conversation
The release shipped with only the git-lfs 'Added' bullet. The tmux guard fix is the half that matters to already-installed hosts - 1.13.2 and 1.13.3 left no-sudo hosts without tmux config - and a reader of the changelog had no way to know it was fixed or that those hosts need a re-run. Doc-only.
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
2 participants
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.
The v1.14.0 entry listed only git-lfs. The tmux guard fix in that same release is the part that affects already-deployed hosts: 1.13.2 and 1.13.3 left no-sudo hosts without
.tmux.conf,.tmux.conf.localandtmux-status-rows, and the entry gave a reader no way to know it was fixed or that those hosts needinstall.shre-run.Doc-only; no code touched. The GitHub release notes for v1.14.0 will be updated to match once this lands.