winget-release
GistGetのWinGetパッケージリリースを支援。(1) 新バージョンのリリース、(2) WinGetマニフェスト作成・更新、(3) winget-pkgsへのPR作成。「WinGetにリリース」「winget-pkgsにPR」「マニフェスト作成」などのキーワードで使用。
Security Assessment
About winget-release
The winget-release skill is designed to streamline the release process of GistGet as a WinGet package. It addresses the complexity and manual steps involved in packaging, versioning, and publishing applications to WinGet and GitHub. By providing an automated, scripted workflow, it reduces human error and ensures that releases are consistent, properly tagged, and compatible with the winget-pkgs repository.
The skill's main capabilities include updating the project version, maintaining a changelog, performing quality checks, building the package, generating ZIP and SHA256 hashes, creating Git tags, publishing GitHub releases, synchronizing with winget-pkgs, generating manifests, and automatically creating pull requests. All these steps are consolidated into a single PowerShell Core script, `Publish-WinGet.ps1`, which serves as the sole release pipeline. The script supports both dry-run previews and full releases, ensuring that users can verify their changes before executing the final release.
Typical use cases involve developers and maintainers of GistGet who want to release new versions efficiently. Target users are those familiar with Git, PowerShell, and the WinGet ecosystem, seeking a reliable and automated approach to update manifests, create pull requests, and publish releases without manual intervention. This skill is particularly valuable for teams aiming to maintain accurate versioning, prevent tagging errors, and streamline the overall release process.
FAQ
How do I start a new release with winget-release?
First, update the <Version> in src/GistGet/GistGet.csproj and add an entry to CHANGELOG.md. Commit and push your changes, then run Publish-WinGet.ps1 with the desired version.
Can I preview the release before executing it?
Yes, you can run the script with the -DryRun option to preview the release without making any permanent changes.
What systems or environments are required to use this skill?
You need PowerShell Core and access to GitHub. The script handles UTF-8 release notes to prevent character encoding issues.
Does the script handle pull requests to winget-pkgs automatically?
Yes, Publish-WinGet.ps1 automatically generates a pull request to the winget-pkgs repository as part of the release process.
Are there any limitations I should be aware of?
Publish-WinGet.ps1 is the only supported release flow; older GitHub Actions workflows have been removed to prevent hash mismatches. Ensure all version and changelog changes are committed before running the script.
Install winget-release
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
nuitsjp/GistGet