Use trunk version in the git repo

描述

贡献者指南

技术栈

javascriptnodejs

领域

clideveloper experiencetooling

议题类型

feature

难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。

3

预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。

1-3 hours

活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。

fresh

清晰度议题是否清楚说明期望改动、验收标准和下一步。

clear

前置要求

Node.js basicsGit basicsUnderstanding of package.json version field

新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。

65

研究方向

Look at the existing build process in package.json and scripts (e.g., build script, version command). Investigate how the current version string is generated (likely from package.json). Then, integrate `git describe tags` or `git rev parse HEAD` during build to embed the commit hash into the CLI header. Check if there's a build step that sets a global constant or reads a file. The issue suggests modifying the header output to include the revision. Consider using a prebuild step to generate a version.ts file with the hash.