@vedantmgoyal9 Looking over this, it seems to still be waiting for info regarding the chosen version? ie is choosing a fixed version/tag (likely known to work) better than choosing the main branch and whatever instability that can cause.

@lucydodo With a GitHub username change like this, I guess we should try contacting the previous account holder to verify it's indeed the same person, just to be on the safe side. 😄

@vedantmgoyal9 ping?

Hello,

Apologies for missing the mention. The action is a wrapper around Komac (a tool developed by a winget-pkgs moderator for manifest creation and submission) with some extra pre and post commands to provide extra functionality.

Previously, I was using a JavaScript-based GH-action, which involved updating npm dependencies and hence, versioning the action. But now, I've rewritten the action in PowerShell as a composite GH-action, removing external dependencies and reducing vulnerability risks. This new setup performs the same tasks without requiring frequent updates, unless there are major changes in PowerShell or Komac's command-line interface.

Thanks for the info @vedantmgoyal9. 😄

@lucydodo Is the above ok with you?

@vedantmgoyal9 ping?

@justinclift might be that you wanted to ping @vedantmgoyal2009 instead?

@mgrojo Nah, it seems like it was an actual username change on GitHub.

For example, even trying to load the old repository (https://github.com/vedantmgoyal2009/winget-releaser) automatically bounces to the new repository location (https://github.com/vedantmgoyal9/winget-releaser).

I've seen that happen before with official repository transfers between accounts, so (to me) that seems to line up ok.

LGTM. Thanks for the contribution.