Community catalog workflows: make tag-pinned download_url a MUST and reject `releases/latest/`
@Shaurya2k06 已经在做这个了。
开始于 2026年8月19日。
评估
这个 Issue 还没有评估数据。
描述
Problem
The community-catalog agentic workflows only softly require a version-pinned download_url. Step 2d currently says the URL "should follow the pattern" — advisory language an autonomous run can rationalize around.
This surfaced in PR #4183 (update speckit-superpowers-bridge to v1.2.0), where the run switched the URL to a floating "latest" alias and validation passed it:
- .../releases/download/v1.1.0/speckit-superpowers-bridge-v1.1.0.zip (tag-pinned)
+ .../releases/latest/download/speckit-superpowers-bridge.zip (floating "latest")
…/releases/latest/download/… is neither of the two accepted tag-pinned patterns. It resolves to whatever the newest release happens to be, not to the <tag> (v1.2.0) recorded in the entry — so the catalog would keep serving the author's future releases under the pinned "version": "1.2.0" record. That's an integrity/reproducibility hole and breaks the convention (all existing catalog download_urls are tag-pinned; none use releases/latest).
The run passed validation because the checks only confirmed the URL returns HTTP 200 and that a v1.2.0 release exists — neither verifies the URL is pinned to the v1.2.0 tag.
Affected workflows
Same soft wording appears in all three community-catalog workflows:
.github/workflows/add-community-extension.md:110.github/workflows/add-community-bundle.md:123.github/workflows/add-community-preset.md:164
Proposed changes
- Change "should follow the pattern" → MUST for the tag-pinned
download_urlrequirement in all three workflows. - Add an explicit rejection rule: a
download_urlwhose path containsreleases/latest/fails validation, even if it returns HTTP 200. - Strengthen the release check to verify the URL's
<tag>segment matches the submittedv<version>(not just that a release exists and a URL 200s).
Accepted URL patterns (unchanged)
https://github.com/<owner>/<repo>/archive/refs/tags/v<version>.ziphttps://github.com/<owner>/<repo>/releases/download/<tag>/<asset>.zip
Context
- PR #4183
- 主要语言
- Python
- 星标
- 138k
- 派生
- 12.4k
- 平均合并
- 3 天 6 小时
- 30 天内合并 PR
- 136
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
github/spec-kit 的其他 Issue
-
triage-can-wait
难度 2/5 1-3 小时 新手友好度 68/100
-
enhancement needs-triage triage-can-wait
难度 2/5 1-3 小时 新手友好度 62/100
-
bundle-submission needs-info triage-can-wait validation-failed
难度 2/5 1-3 小时 新手友好度 78/100
-
author-awaiting enhancement needs-triage preset-submission triage-can-wait validation-failed
难度 2/5 1-3 小时 新手友好度 72/100
-
author-awaiting enhancement extension-submission needs-triage triage-can-wait validation-failed
难度 2/5 1-3 小时 新手友好度 68/100
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 82/100
-
难度 2/5 1-3 小时 新手友好度 88/100
use-agent-os/agent-os#3314 ·
-
难度 2/5 1-3 小时 新手友好度 75/100
BasedHardware/omi#15662 · 1 条评论 ·
-
documentation help wanted
难度 2/5 1-3 小时 新手友好度 90/100
-
难度 2/5 1-3 小时 新手友好度 62/100
AiursoftWeb/AnduinOS-2#19 ·