chore(cli): support Winget publishing#5615
Draft
jgoux wants to merge 1 commit into
Draft
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changed
Adds Winget publishing support for stable Supabase CLI releases using WingetCreate instead of maintaining custom Winget manifest YAML generation.
The release workflow now keeps Winget publishing behind
WINGET_PUBLISH_ENABLED, so the firstSupabase.CLIsubmission can land inmicrosoft/winget-pkgsbefore CI starts submitting updates. Once enabled, stable releases call the new PowerShell wrapper to runwingetcreate updatewith the released Windows x64 and arm64 ZIP URLs.The release docs and distribution ADR now describe the two-phase rollout: one-time bootstrap PR first, then automated WingetCreate updates from release CI.
Reviewer notes
The functions deploy realpath adjustment is included because the CLI integration suite exposed a macOS
/varversus/private/varpath mismatch while validating this branch.