What is the areas you experience the issue in?
Go-COSE Library
What is not working as expected?
dependabot sents PRs for upgrading go-cose from v1.1.0 to v1.2.0. For instance: notaryproject/notation-go#329
The godoc for v1.2.0 is available but there is no tag or release in this repo related to 1.2.0.
@setrofim @yogeshbdeshpande @qmuntal @thomas-fossati Is v1.2.0 mis-released? If so, we should retract the release, and the next release should be v1.3.0.
What did you expect to happen?
In go.mod, have an entry
retract (
v1.2.0 // Published accidentally.
v1.2.1 // Contains retractions only.
)
How can we reproduce it?
PS D:\Test\go> go get github.com/veraison/go-cose
go: downloading github.com/veraison/go-cose v1.2.0
go: added github.com/fxamacker/cbor/v2 v2.4.0
go: added github.com/veraison/go-cose v1.2.0
go: added github.com/x448/float16 v0.8.4
Describe your environment
All platforms
What is the version of your Go-COSE Library?
v1.2.0
What is the areas you experience the issue in?
Go-COSE Library
What is not working as expected?
dependabot sents PRs for upgrading
go-cosefromv1.1.0tov1.2.0. For instance: notaryproject/notation-go#329The godoc for v1.2.0 is available but there is no tag or release in this repo related to
1.2.0.@setrofim @yogeshbdeshpande @qmuntal @thomas-fossati Is
v1.2.0mis-released? If so, we should retract the release, and the next release should bev1.3.0.What did you expect to happen?
In
go.mod, have an entryHow can we reproduce it?
Describe your environment
All platforms
What is the version of your Go-COSE Library?
v1.2.0