Bump go-git to v5.19.0 and go-billy to v5.9.0#197
Merged
Conversation
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.
go-billy v5.9.0 changed
osfsto resolve symlinks inRoot(), so on macOSWorkDir()now returns/private/var/...instead of/var/.... Same path, just the resolved form. Production callers only use it to open files or ascmd.Dir, so nothing changes there; three test assertions that compared against unresolvedt.TempDir()paths needed normalizing.createTestReponow resolves its temp dir before returning, which also let the worktree test drop its separateresolvedRepoDirstep since both sides agree now.go-git v5.19.0 requires go-billy v5.9.0 so they move together. Neither contains the upstream fixes worked around in #194/#196; this is just keeping current. Transitively pulls
golang.org/x/{crypto,mod,net,sys,text,tools}andpjbgf/sha1cdforward.