-
Notifications
You must be signed in to change notification settings - Fork 974
Closed
Labels
must-doIssues that must be completed by the end of the Sprint. Or else. Only humans may set this.Issues that must be completed by the end of the Sprint. Or else. Only humans may set this.s4Internal bugs (e.g. test flakes), extreme edge cases, and bug risksInternal bugs (e.g. test flakes), extreme edge cases, and bug risks
Description
Description
Take a look at - https://github.com/coder/coder/actions/runs/7611646446/job/20727993997 (and other release runs)
Publishing to winget failed because:
Submitting pull request for manifest...
Unable to create a reference to the forked repository. This can be caused when the forked repository is behind by too many commits. Sync your fork and try again.
Error: Process completed with exit code 1.
Steps to fix
This will reproduce for subsequent releases/runs until the fork used for submitting PR is kept in sync with upstream.
i.e., https://github.com/cdrci/winget-pkgs in this case
WingetCreate does attempt to sync the fork before making a PR, but that can fail if the fork is behind too many commits.
Suggest to make it as part of CI to sync the fork (through gh
CLI?) before winget publish step to avoid this in the future
Upstream issue
Related to:
matifali
Metadata
Metadata
Assignees
Labels
must-doIssues that must be completed by the end of the Sprint. Or else. Only humans may set this.Issues that must be completed by the end of the Sprint. Or else. Only humans may set this.s4Internal bugs (e.g. test flakes), extreme edge cases, and bug risksInternal bugs (e.g. test flakes), extreme edge cases, and bug risks