Not sure how to test it. Will it submit the package in my name or the coder

To push an update, we first need to create a package for the first time that is interactive and manual.
I am not sure if it has to be created using Coder Inc. GitHub or if I can do it from my account.
Meanwhile, I have created a PR here also,
microsoft/winget-pkgs#86416
and tried to fill in all the required metadata from coder.com/

Also,
A GitHub Personal Access token is required to submit packages to winget community repo.

https://github.com/microsoft/winget-create/blob/main/doc/token.md

Please create a token as shown here and store it as a secret in GITHUB_PAT

Or maybe the existing GITHUB_TOKEN be used. It's a test.
@deansheather

To push an update, we first need to create a package for the first time that is interactive and manual.
I am unsure if it has to be created using Coder Inc. GitHub or if I can do it from my account.
Meanwhile, I have created a PR here also,
microsoft/winget-pkgs#86416
and tried to fill in all the required metadata from coder.com/

My PR was closed as a duplicate of microsoft/winget-pkgs#86238, I did not check that you have already submitted a PR.

I'll do a review pass of this PR on Monday and get it merged for you. We'll sort out the bounty payout post-merge cc @ghuntley

I updated your PR to use GH CLI instead of pinging the API directly (to avoid potential ratelimits), as well as updated it to comment on the PR pinging me so microsoft maintainers can get in contact with me if something's wrong.

I also discovered that the file version I was inserting into the installer binary was incorrect so I fixed that as well.

I updated your PR to use GH CLI instead of pinging the API directly (to avoid potential ratelimits), as well as updated it to comment on the PR pinging me so microsoft maintainers can get in contact with me if something's wrong.

I also discovered that the file version I was inserting into the installer binary was incorrect so I fixed that as well.

Yes, it looks like a better approach. Yes, the installer version had the 4th section as the release date.
Also, to test this in production it should be merged before the next release.

Thanks for sending in the pull-request @matifali I'm going to have a look/review after lunch. A quick note to say haven't forgotten!