chore: install the whole build, run and test toolchain through mise, and consider mise tasks in place of Taskfile

未关闭
#178 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
12/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
go, python, yaml

调研方向

Start with mise.toml, the go.tool*.mod files, Taskfile.yml and .github/actions/install-task/action.yml to see how tools are installed today. Then read internal/upgrade/taskfile_shape_test.go, which pins the CI jobs to task targets, and scripts/vuln_report.py, which lists the tool roster. Done means the D-04 tool-sourcing decision and the task-runner decision are recorded, with the required job names still intact. This is design work, so check with the maintainer before writing any code.

由索引模型根据 Issue 内容生成。

描述

area:ci chore priority:low tracking

The build, run and test tools reach a machine in four different ways, and none of them pins the Go toolchain itself. Move the whole tool suite into mise, and consider mise tasks in place of Taskfile.yml.

What exists today (main at 8c0107f1)

  • Go tools are built from five isolated modfiles:

    • go.tool.mod: task, goreleaser, govulncheck
    • go.tool-changie.mod: changie
    • go.tool-golangci.mod: golangci-lint
    • go.tool-lint.mod: actionlint
    • go.tool-proto.mod: buf, protoc-gen-go, protoc-gen-connect-go

    CI builds task through .github/actions/install-task, and the Taskfile runs the rest through go tool -modfile=....

  • Go comes from actions/setup-go with go-version-file: go.mod in CI, and from whatever Go is on the machine locally. Ambient Go 1.27 cannot build cockroachdb/swiss, so every local task test needs GOTOOLCHAIN=go1.26.10, and the Taskfile hard-codes that pin in several places (#104).

  • Node and pnpm: actions/setup-node (Node 24) and web/package.json's packageManager: [email protected].

  • mise already pins hk and @fission-ai/openspec in mise.toml, with mise.lock for linux-x64, linux-arm64 and macos-arm64.

  • Python is the runner's python3. #177 covers it.

  • Tasks: Taskfile.yml holds about 6,200 lines and 73 top-level tasks. CI runs task <target> in every workflow (43 uses in ci.yml).

What to do

  • Pin every tool in mise.toml: Go (from go.mod's go line, which also closes the local half of #104), task or its replacement, goreleaser, govulncheck, changie, golangci-lint, actionlint, buf and the protoc plugins, Node, pnpm, uv, hk and openspec. Keep mise.lock for all three platforms.
  • Use one bootstrap for local and CI. Locally that is mise install. In CI it is either jdx/mise-action or a composite action that keeps D-04 (below).
  • Retire the go.tool*.mod files once mise owns those tools, and point the tool roster that task vuln scans (scripts/vuln_report.py) at the mise-installed binaries.
  • Evaluate mise tasks ([tasks] in mise.toml, or file tasks under .mise/tasks/) as a replacement for Taskfile.yml, as a separate step after the tools move.

Decisions needed

  • D-04, how CI gets tools. .github/actions/install-task/action.yml says every CI build tool is built from the checksummed Go module proxy and never from a GitHub Releases download or an install script, after CDN outages broke arduino/setup-task and taskfile.dev/install.sh in holomush. mise's go: backend keeps that for the Go tools, because it runs go install through the proxy. The aqua: and ubi: backends, and jdx/mise-action itself, download release binaries. Decide per tool, and record the decision.
  • Taskfile vs mise tasks. internal/upgrade/taskfile_shape_test.go makes every ci.yml job a registered task <target> run (inScopeJobs, runBodyExceptions). Moving to mise tasks means rewriting that guard. Several Taskfile targets also carry long, load-bearing comments: the golden suite, the tmux e2e, release rehearsal and fragment checks.
  • Required checks. The protect-main ruleset pins its required checks by job name. The migration must keep every job name.

Suggested order

  1. Pin Go, Node, pnpm and uv in mise, and use them locally.
  2. Move the Go-built tools to mise go: entries, and switch CI bootstrap with D-04 kept or explicitly revised.
  3. Decide on the task runner.

Related: #104 (Go toolchain pin), #177 (uv), #176 (the mutation-check script).

🤖 Generated with Claude Code

https://claude.ai/code/session_016kpFpXsCNuZSmh5X7ebdwU

主要语言
Go
星标
0
派生
0
平均合并
7 小时 42 分钟
30 天内合并 PR
111

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

seanb4t/codegraph-go 的其他 Issue

查看 seanb4t/codegraph-go 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。