Cut v1.3.0-alpha.1 Release

[SteveLasker]

@veraison/go-cose-maintainers, please +1 to create a v1.2.0-alpha.1 release, or create/reference issues or new PRs that should be considered prior.

[SteveLasker]

@shizhMSFT, @setrofim, @qmuntal, @thomas-fossati, @yogeshbdeshpande, @roywill
Please provide your vote for a release.

[shizhMSFT]

@SteveLasker Could you specify the commit proposed to be tagged as v1.2.0-alpha.1?

[SteveLasker]

Great question. We should make a template for releases

Let’s start with: 8c458e2

[yogeshbdeshpande]

+1 for release

[setrofim]

+1

[SteveLasker]

Released: https://github.com/veraison/go-cose/releases/tag/v1.2.0-alpha.1
Need to resolve the version #

[SteveLasker]

see #192

[shizhMSFT]

@SteveLasker @yogeshbdeshpande @setrofim It seems that v1.2.0-alpha.1 is released. Note that as a golang library, it is released as long as there is a new tag no matter whether a release page is created or not.

I also noticed that we previously published v1.2.0 in error and retracted it in v1.2.1. Technically, our next version should be v1.3.0-alpha.1 not v1.2.0-alpha.1.

[shizhMSFT]

Linking

• Is go-cose v1.2.0 mis-released? #152
• Retract v1.2.0 release #153

[SteveLasker]

I saw the retraction after digging in.
Does anyone have a concern jumping to v1.3.0-alpha.1 ?

[OR13]

We should make sure the latest release matches to the latest tag.

[SteveLasker]

Updated the title to reflect the updated version

[SteveLasker]

https://github.com/veraison/go-cose/releases/tag/v1.3.0-alpha.1