Quickstart 2.0 Workflow fails probably because of yaml parsing `1.20` -> go 1.2

[fwilhe2]

Just noticed that all available runs of the 'quick start 2.0' workflow failed probably because of this weird yaml thing where go 1.20 is parsed as version 1.2. The fix should be to quote the version number so it is a string.

I'm not sure if this is actually causing the error, but I guess the setup-go action can't deal with that ancient go version.

[Ankita13-code]

Hi @fwilhe2
I'm a new here and have been trying out Mariner for quite some time now and I want to start making some contributions. I'd like to take up this issue. Could you please assign it to me?

[fwilhe2]

Hi @Ankita13-code, I don't work for MSFT and I never contributed to this repo, so I can't assign you. I was just curious that this seems to be broken for so long without any issue or PR I could find to address the issue. Hope some of the maintainers can help you.

[cwyborny]

I have this failure daily on my fork with this error: The process '/usr/bin/git' failed with exit code 1
Not sure how I can fix that..

[fwilhe2]

Not sure how I can fix that..

Your fork does not have a '2.0-stable' tag, cf https://github.com/microsoft/CBL-Mariner/tree/2.0-stable. That's not related to the issue I opened.

If you push/create that tag it should fail with the same error as upstream. I think you can select this when forking a repo on github.

[dmcilvaney]

Hey, thanks for noticing this!

I ran into something similar a while ago, might be inspiration for a fix (#6329).

If you want to take another swing at a fix go for it, otherwise I'll take a look in a bit and see if I can figure out what's going wrong.

[fwilhe2]

Hi @dmcilvaney, please go ahead, I'm not planning to work on this. Just wanted to know if my guess about the low effort fix was right, but obviously it was not.

[mfrw]

Unsure, if :

• workflows: bump setup-go to v5 #7262

fixes it ?

/cc @dmcilvaney

[mfrw]

Hi @fwilhe2 I'm a new here and have been trying out Mariner for quite some time now and I want to start making some contributions. I'd like to take up this issue. Could you please assign it to me?

@Ankita13-code - Feel free to take a stab at it :)