gorelease printed two diagnostics and returned exit code 1
# diagnostics
required module github.com/microcosm-cc/bluemonday@v1.0.23 retracted by module author: Retract older versions as only latest is to be depended upon
required module go.mongodb.org/mongo-driver@v1.11.0 retracted by module author: Retract v1.11.0 through v1.11.2 because they contain a data race bug in
What did you expect to see?
I do not expect to see the diagnostics, because I do not have those modules listed in my go.mod as either direct or indirect dependencies.
I was able to get gorelease working by introducing a dependency on the retracted modules (which otherwise won't be in my go.mod after running "go mod tidy").
Once depending on these dependencies (which I don't otherwise need). I was able to "go get" to get non-retracted versions.
go get github.com/microcosm-cc/bluemonday@v1.0.26
go get go.mongodb.org/mongo-driver@v1.15.0
The end result is that I've added extra unneeded dependencies to my project to make it so gorelease won't fail. This is definitely not working as intended.
Go version
go 1.22.2
Output of
go env
in your module/workspace:What did you do?
I have run gorelease.
What did you see happen?
gorelease printed two diagnostics and returned exit code 1
What did you expect to see?
I do not expect to see the diagnostics, because I do not have those modules listed in my go.mod as either direct or indirect dependencies.
I was able to get gorelease working by introducing a dependency on the retracted modules (which otherwise won't be in my go.mod after running "go mod tidy").
Once depending on these dependencies (which I don't otherwise need). I was able to "go get" to get non-retracted versions.
The end result is that I've added extra unneeded dependencies to my project to make it so gorelease won't fail. This is definitely not working as intended.