Automate winget updates per release and dry-run the manifest step
维护者通常 3 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 47/100
调研方向
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 内容生成。
描述
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 thereleasejob ("Update the Scoop and winget manifests on main"): untested, pushes tomainwithGITHUB_TOKEN, relies onpythonon the runner and onmainnot 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
- Move manifest generation into a reusable job that can be triggered with
workflow_dispatchfor 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. - 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. - 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
mainand a winget-pkgs PR without manual steps.
- 主要语言
- Python
- 星标
- 0
- 派生
- 2
- 平均合并
- 2 天 13 小时
- 30 天内合并 PR
- 2
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
TMHSDigital/autoclicker 的其他 Issue
-
maintenance priority: low
难度 3/5 半天 新手友好度 56/100
TMHSDigital/autoclicker#202 ·
维护者通常 3 天内回复
-
bug priority: low
难度 3/5 1-2 天 新手友好度 52/100
TMHSDigital/autoclicker#201 ·
维护者通常 3 天内回复
-
dependencies maintenance priority: medium
难度 5/5 一周以上 新手友好度 35/100
TMHSDigital/autoclicker#154 · 1 条评论 ·
维护者通常 3 天内回复
-
marketing packaging priority: low
难度 4/5 3-5 天 新手友好度 38/100
TMHSDigital/autoclicker#118 · 1 条评论 ·
维护者通常 3 天内回复
-
documentation marketing priority: medium
难度 3/5 1-2 天 新手友好度 55/100
TMHSDigital/autoclicker#117 · 1 条评论 ·
维护者通常 3 天内回复
查看 TMHSDigital/autoclicker 的全部 Issue
相似的 Issue
-
hive size:simple
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
A new VOLTTRON_HOME starts with agent isolation mode on (string comparison of a boolean default)未关闭
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 70/100
painted-porch/marcus#977 ·
维护者通常 1 天内回复
-
llm translation
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
FAIRmat-NFDI/sand#239 ·
维护者通常 1 天内回复