Add scheduled workflow to sync winget-pkgs fork #283
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The smallstep/winget-pkgs fork drifted ~86K commits behind microsoft/winget-pkgs, causing winget releases to fail with API errors. This workflow syncs the fork monthly to prevent drift. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
smallstep/winget-pkgsfork withmicrosoft/winget-pkgsContext
The Winget release flow stopped working 7 months ago, I think it was because the fork drifted ~86K commits behind upstream. When goreleaser tried to sync the fork during release, it failed with 502/500 errors due to the massive divergence.
This workflow prevents that by keeping the fork reasonably up to date.
Test plan
GORELEASER_PATsecret has access tosmallstep/winget-pkgs🤖 Generated with Claude Code