Detect relative local git repo paths in a more reliable way #212
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.
Fixes #211
When doing our special git monorepo install logic, we have to resolve local relative repo paths to absolute paths, so that when we reference them from a temp directory, they are pointing to the right location. Previously we did that by assuming anything that wasn't a URL was a local path, but this is actually wrong because of repo specifiers like
git@github.com:MyOrg/my-repo.git
. Instead, now we check for.
prefix, which is simpler and works fine because only filepaths should ever start with a.
.Also bump dependencies and prepare a patch release.