-
Notifications
You must be signed in to change notification settings - Fork 18k
x/exp/cmd/gorelease: report requirements on retracted module versions #37781
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Impl note: Impl note: definitely should report direct dependencies, maybe transitive. |
In particular, the command below will list retracted dependencies in a machine-readable format.
|
Arrived here on the back of trying out module retractions
I would say definitely should report transitive deps. After all, a module is marked as retracted for at least the following reasons:
(quoting #24031 (comment)) I would suggest this is a fairly important feature to land "soon". Reason being, |
(starting work in https://go-review.googlesource.com/c/exp/+/310370) |
Change https://golang.org/cl/310370 mentions this issue: |
Note: this format seems to not work for me :(
I'm able to get programmatic output with
|
Ah, nevermind, I see the issue: I was able to get at the same thing with:
|
Fixes golang/go#37781 Change-Id: I109ce5da26c757e7e1bdd6bdcee0ff14be35230b Reviewed-on: https://go-review.googlesource.com/c/exp/+/310370 Trust: Jean de Klerk <deklerk@google.com> Run-TryBot: Jean de Klerk <deklerk@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Jay Conrod <jayconrod@google.com>
A mechanism for retracting module versions is described in #24031, specifically in this comment.
gorelease
should report an error if the module requires a retracted module version directly or transitively. This will help module authors avoid depending on retracted versions.The text was updated successfully, but these errors were encountered: