Add explicit version instructions to README #1015
Closed
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
|
@eouw0o83hf The v2 issue should have been resolved by #998. Now if I run |
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.
Background
I am working on implementing ent in a codebase. The testing page of ent specifically recommends using this repository.
go getting this repository installs an invalid version which only fails in a way that's really difficult to analyze. Figuring out what the root cause was and figuring out how to install the correct version has eaten up an unfortunate chunk of my day.Change
It looks like there's some other work going on in PRs to remediate the version issue. This doesn't pretend to fix that, but gives developers who wind up on this page a really explicit and easy way to solve that versioning problem before it wrecks their days.
Cheers!