Updating release-winget according to manifest schema changes

[ldennington]

It appears that changes have been made to the winget schema since this workflow was created, so I've made the necessary updates here. Additionally, we've fixed a couple issues in the mjcheetham/update-winget task that had been causing this workflow to fail (see this and this).

With these updates, we should be good to go to publish gcm core to winget automatically with the next release. Exciting times!

I validated this workflow locally by successfully opening a PR against my winget-playground repo and running winget validate to ensure the generated manifest adheres to winget's required schema.

[derrickstolee]

Wow, they really broke backwards compatibility with these manifest changes. Do you have a link to the full spec? I wonder if there are some other fields we might want to populate (do Description or LongDescription exist?).

[derrickstolee]

Is there now a longer Description: that we should populate somehow?

[ldennington]

Description does still exist. However, for reasons that aren't super clear, ShortDescription is now required, while Description is not. I'm happy to take a stab at adding a longer Description though!

[ldennington]

Is there anything specific we'd want to call out in a longer Description?

[derrickstolee]

I think we can wait on Description until we know more about where it will show up.

[ldennington]

Wow, they really broke backwards compatibility with these manifest changes. Do you have a link to the full spec? I wonder if there are some other fields we might want to populate (do Description or LongDescription exist?).

Yep. I was pretty shocked tbh. Here's the link to the spec, and some documentation around it that I felt was helpful. I'm happy to add whichever extra fields we feel are helpful!

[derrickstolee]

Wow, they really broke backwards compatibility with these manifest changes. Do you have a link to the full spec? I wonder if there are some other fields we might want to populate (do Description or LongDescription exist?).

Yep. I was pretty shocked tbh. Here's the link to the spec, and some documentation around it that I felt was helpful. I'm happy to add whichever extra fields we feel are helpful!

Ah, there seems to be a Description item in addition to the ShortDescription.

[derrickstolee]

I think we still want repo: microsoft/winget-pkgs, right? Or, is that built-in to v1.2?

[ldennington]

It's the default! However, we can keep if it's better to be explicit.

[derrickstolee]

Thanks! Using the default works for me.