release-winget.yml: fix submission pwsh script#747
release-winget.yml: fix submission pwsh script#747dscho merged 1 commit intomicrosoft:vfs-2.49.0from
Conversation
|
Strangely, I needed a couple of updates, until the deployment finally worked: microsoft/winget-pkgs#251831. I will force-push the PR branch as soon as CI has finished (so that the |
dscho
left a comment
dscho
left a comment
There was a problem hiding this comment.
Verified by this workflow run which opened microsoft/winget-pkgs#251831
|
What the hay? This is starting to get ridiculous. I know that a team of two is very small, but how is this supposed to work for us? The ruleset prevents all of us two team members from merging. This is not going to work. |
During a refactoring I accidentally omitted the `$manifestPath` variable that is required to determine the `$manifestDirectory` for the submission command to WinGet. Since the directory is just a constant, let's update the submission command. Signed-off-by: Matthew John Cheetham <mjcheetham@outlook.com> Signed-off-by: Johannes Schindelin <johasc@microsoft.com>
So apparently it was not merely the last push, but force-pushing to a tree-same commit does not lift that restriction. Surprising, and not what the message said. |
2 participants
During a refactoring I accidentally omitted the
$manifestPathvariable that is required to determine the$manifestDirectoryfor the submission command to WinGet. Since the$manifestDirectoryis just a constant, let's update the submission command.