T27-53 — Define canonical asset naming and generate every checksum and the release-wide list
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Read docs/RELEASE-ENGINEERING-PLAN.md §4, then inspect xtask/src/dist.rs, .github/workflows/release.yml, and the artifact matrix naming column. The issue identifies T27-06 as a blocker, so first check whether that candidate baseline is available. Done means the naming scheme is documented and cd dist && sha256sum -c RELEASE_SHA256.txt verifies the full published set, including provenance and signature files when present.
由索引模型根据 Issue 内容生成。
描述
T27 row: T27-53
Work package: RP-06 — Supply-chain metadata, provenance, signatures, workflow hardening
Priority: P0
Status: NOT STARTED
Objective
Establish one canonical asset-naming scheme and one checksum list that covers every published file, so the aggregate can be checked deterministically.
Acceptance criteria: The naming scheme is written down; every asset carries a SHA-256; one release-wide checksum list covers every published file, including the provenance and signature files when they exist; the list verifies with sha256sum -c.
Inputs
xtask/src/dist.rs (MANIFEST.sha256 generation); .github/workflows/release.yml (the RELEASE_SHA256.txt generation step); the artifact matrix's artifact-name column.
Authority
docs/RELEASE-ENGINEERING-PLAN.md §4 — every published asset has a verified SHA-256 and a release-manifest entry; the aggregate fails closed on mislabeled or mismatched assets.
Stopping condition
The naming scheme is documented and the checksum list verifies across the full published set.
Verification
cd dist && sha256sum -c RELEASE_SHA256.txt
Evidence and blockers
release.yml generates RELEASE_SHA256.txt for 7 files — it does not yet cover provenance or signature files, which do not exist. The canonical naming scheme itself is not written down anywhere, so two builds could disagree on a name without either being wrong by inspection.
Blocker: T27-06 (the candidate baseline).
Ledger: docs/tasks/T27-53-asset-naming-and-checksums.md and docs/release/EXECUTION-BOARD.md row T27-53 (these land with PR #12).
Campaign: docs/planning/release-compaign/Cross-Platform Releas.txt.
- 主要语言
- Rust
- 星标
- 11
- 派生
- 1
- 平均合并
- 9 小时 48 分钟
- 30 天内合并 PR
- 13
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
aliasfoxkde/FireCraft 的其他 Issue
-
documentation release
难度 2/5 1-3 小时 新手友好度 68/100
aliasfoxkde/FireCraft#58 ·
维护者通常 1 天内回复
-
release
难度 4/5 3-5 天 新手友好度 54/100
aliasfoxkde/FireCraft#81 ·
维护者通常 1 天内回复
-
documentation
难度 5/5 一周以上 新手友好度 35/100
aliasfoxkde/FireCraft#80 ·
维护者通常 1 天内回复
-
enhancement parity
难度 4/5 3-5 天 新手友好度 48/100
aliasfoxkde/FireCraft#79 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 38/100
aliasfoxkde/FireCraft#78 ·
维护者通常 1 天内回复
查看 aliasfoxkde/FireCraft 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
bug CLI
难度 2/5 1-3 小时 新手友好度 77/100
HigherOrderCO/Bend#2120 ·
-
难度 2/5 1-3 小时 新手友好度 66/100
KNXBench-Labs/KNXBench#47 ·
-
难度 2/5 1-3 小时 新手友好度 88/100
software-mansion/pathfinder#3620 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复