chore: Matching the /x/crypto Level to the Go Mod Level #49
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.
Name of feature:
Matching Go Mod Go Level to Dep Level
Pain or issue this feature alleviates:
Go 1.14 does not support x/crypto 0.33.0
x/ packages don't support the backwards compat promise, so this go.mod stating Go 1.14 support, should ensure that the corresponding packages (x/crypto in this case) can support the stated Go level - Specifically, this creates a co-req with x/net 0.25.0 in most codebases which results in an error like (NetConn was added in Go 1.18).
0.14.0 is guarunteed to work with Go 1.14 which is the stated go mod compatibility level
Why is this important to the project (if not answered above):
go.mod should be consistent
Is there documentation on how to use this feature? If so, where?
Non-functional
In what environments or workflows is this feature supported?
All, this library does not depend on any x/crypto features from future releases and does not benefit from any version bumps.
In what environments or workflows is this feature explicitly NOT supported (if any)?
Supporting links/other PRs/issues:
💔Thank you!