Skip to content

ci: publish releases to winget - #528

Open
gmegidish wants to merge 1 commit into
mainfrom
ci/winget-publish
Open

gmegidish wants to merge 1 commit into
mainfrom
ci/winget-publish

Conversation

@gmegidish

@gmegidish gmegidish commented Oct 17, 2026 •

Copy link
Copy Markdown
Member

Adds a winget job that runs after publish on tag builds and submits an updated manifest for MobileNext.mobilecli to winget-pkgs via vedantmgoyal9/winget-releaser@v2.

  • Installers: mobilecli-<version>-windows-{amd64,arm64}.zip from the GitHub release
  • Version/tag: github.ref_name (tags have no v prefix)

Before merging

  • First version must be submitted manually (komac new MobileNext.mobilecli); the action only updates existing packages
  • Add WINGET_TOKEN repo secret (classic PAT with public_repo, owner needs a fork of microsoft/winget-pkgs)

Test plan

  • Next tag release: winget job opens a PR on microsoft/winget-pkgs

Summary by CodeRabbit

  • New Features
    • Windows users can install MobileCLI through the Winget package manager for tagged releases.

@coderabbitai

coderabbitai Bot commented Oct 17, 2026 •

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Repository: mobile-next/mobilecli/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Essentials
  • Run ID: d4ca31bd-4bef-40ba-991c-dcd7bb96bdb5
📥 Commits

Reviewing files that changed from the base of the PR and between 77128e8 and 003de17.

📒 Files selected for processing: 1
  • .github/workflows/build.yml

Included review availability: This review used your included allowance. 2 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 3 reviews per hour.

📝 Walkthrough

The build workflow adds a tag-triggered Windows job that runs after publish. It invokes the Winget releaser for MobileNext.mobilecli and uses the tag as the version and release tag.

Changes: Winget Release

Layer / File(s) Summary
Configure Winget release job
.github/workflows/build.yml
The workflow runs the Winget releaser on windows-latest after publish. It matches amd64 and arm64 ZIP installers and authenticates with WINGET_TOKEN. A comment notes that the first manifest submission is manual.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to 003de

The Winget job uses the repository’s release version and waits for the matching Windows archives to be published; no actionable merge risk was established.

Pre-merge checks: Passed 5
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly and concisely describes the main change: publishing releases to Winget through CI.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant