Existing CRT build-input and redistribution evidence for v24.21.0 win-x64
维护者通常 3 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 52/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 领域
- release
调研方向
Start with the release/build records for Node.js v24.21.0 and look for the listed win-x64/node_pdb.zip artifact, its SHA-256, and the embedded MSVC and Windows SDK library provenance. Determine whether retained manifests provide exact input hashes, pinned toolchain package details, and applicable license or notice text. Done means linking each relevant record and stating exactly which embedded CRT inputs and redistribution conditions it covers, or identifying which requested evidence is absent.
由索引模型根据 Issue 内容生成。
描述
We are qualifying the unchanged official v24.21.0 Windows AMD64 binary for
redistribution within an offline commercial application. Could you point to
existing artifact-bound build-input and licensing evidence for the Microsoft
runtime code incorporated into that release?
The binary SHA-256 is
ba4e6d110e8c1592a1ecd390f6b05f3da124b13871a5be62b341a07a853c6c32.
The official win-x64/node_pdb.zip SHA-256 is
122f2af58bfb25816f12e49179217c3ff5bf96c1e083f3ccb0969a5b4794ff85;
the PDB GUID/age matches the executable. Its CRT module paths identify
MSVC 14.44.35207 libcmt.lib, libcpmt.lib, libvcruntime.lib and
Windows SDK 10.0.26100.0 libucrt.lib.
Specifically, we seek any retained exact library hashes/input manifest, pinned
compiler/SDK package provenance, and applicable license/redistribution terms for
those embedded inputs, including any notices or downstream recipient conditions.
We are not asking for unpublished source, signing keys, customer data, a new
build, support commitment or legal advice. If an existing release/build record
already covers this, a link and its exact scope would be sufficient for review.
We distinguish the project's MIT-licensed source from separately licensed
embedded runtime inputs; recorded directory versions alone are not treated as
the input library hashes or an artifact-specific redistribution grant.
- 主要语言
- Jinja
- 星标
- 542
- 派生
- 184
- 平均合并
- 3 天 5 小时
- 30 天内合并 PR
- 10
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nodejs/build 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 3 天内回复
-
Windows/arm machines unavailable可能已有人在做 @StefanStojanovic 于 2 天前认领。 未关闭incident platform:windows
nodejs/build#4511 · 1 条评论 · 1 个 reaction · 已指派 1 人 ·
维护者通常 3 天内回复
-
难度 4/5 一周以上 新手友好度 5/100
维护者通常 3 天内回复
-
build-agenda
难度 4/5 3-5 天 新手友好度 25/100
维护者通常 3 天内回复
相似的 Issue
-
Help-Wanted Needs-Triage Package-Update
难度 1/5 1-3 小时 新手友好度 68/100
microsoft/winget-pkgs#450807 ·
维护者通常 1 天内回复
-
package-update
难度 2/5 1-3 小时 新手友好度 67/100
oSoWoSo/vOid_Community_repOsitory#333 ·
维护者通常 1 天内回复
-
backend bug
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
release_latest republishes the previous tag on an untagged commit and exits 0 when the push fails未关闭
难度 2/5 1-3 小时 新手友好度 84/100
-
难度 2/5 1-3 小时 新手友好度 62/100