Automate winget updates per release and dry-run the manifest step

未关闭
#91 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 3 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
47/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
冷清
技术栈
github-actions, python
领域
devops, release

调研方向

Start with the release job in .github/workflows/ci.yml and the Package managers section of docs/RELEASING.md; inspect how the current manifest step uses Python and GITHUB_TOKEN. Work through the suggested workflow_dispatch dry run for v1.5.0, then the automated winget PR and secret documentation. Done means a dry run succeeds and a new tag updates Scoop and opens a winget-pkgs PR.

由索引模型根据 Issue 内容生成。

描述

ci packaging priority: medium

Why it matters

Future releases need winget updates too, and today each one is manual: a new pull request to microsoft/winget-pkgs per version. Separately, the new release-job step that regenerates the Scoop and winget manifests and pushes them to main has never run. It will run for the first time during the next real release, where a failure marks the release job red after the release is already published.

Evidence

  • .github/workflows/ci.yml, last step of the release job ("Update the Scoop and winget manifests on main"): untested, pushes to main with GITHUB_TOKEN, relies on python on the runner and on main not being protected.
  • docs/RELEASING.md, "Package managers": winget submission is a manual PR. The first one is microsoft/winget-pkgs#446760 (waiting on the CLA).

Suggested approach

  1. Move manifest generation into a reusable job that can be triggered with workflow_dispatch for an existing tag (dry-run mode that only uploads the files as an artifact), and run it once for v1.5.0 to prove it works.
  2. Once the first winget version is merged, add vedantmgoyal9/winget-releaser (pinned SHA) to the release job with a fine-grained PAT stored as a secret, so every tag opens the winget update PR automatically.
  3. Document the secret and the fallback (manual wingetcreate submit) in RELEASING.md.

Done when

  • The manifest step has run successfully at least once outside a real release, and a new tag produces both the Scoop update on main and a winget-pkgs PR without manual steps.
主要语言
Python
星标
0
派生
2
平均合并
2 天 13 小时
30 天内合并 PR
2

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

TMHSDigital/autoclicker 的其他 Issue

查看 TMHSDigital/autoclicker 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。