Skip to content

ci(release): Sync winget-pkgs fork before publishing #11842

@mdanish-kh

Description

@mdanish-kh

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:

Metadata

Metadata

Assignees

Labels

must-doIssues 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 risks

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy