Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Migrate CI setup to pnpm/setup

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

维护者通常 2 天内回复

@EhabY 已经在做这个了。

开始于 2026年9月18日。

  • #1121 来自 @EhabY —— 已关闭,未合并

评估

这个 Issue 还没有评估数据。

描述

tech-debt

.github/actions/setup/action.yml pins three things to get a build environment: pnpm/action-setup for pnpm, actions/setup-node for Node 22, and a pnpm install --frozen-lockfile step. pnpm's continuous integration docs now recommend a single action instead:

- uses: pnpm/setup@<sha> # v2.1.0
  with:
    runtime: node@22
    cache: true

pnpm/setup installs pnpm, installs the runtime with pnpm runtime set and puts it on PATH (replacing actions/setup-node), caches the pnpm store, and runs pnpm install unless you pass install: false. Two pinned actions and an install step collapse into one.

Check before switching

  • Store cache. #1110 moved the store cache to pnpm/action-setup's cache: true, which keys on pnpm-cache-<os>-<arch>-<lockfile hash> and falls back to the last store for the platform, so a dependency bump fetches only what changed. Confirm pnpm/setup keeps that fallback; without it every bump refetches the whole store.
  • Frozen installs. Its automatic pnpm install must stay frozen in CI, as --frozen-lockfile does today. require-lockfile looks related.
  • Windows on ARM64. The windows-11-arm job needs pnpm runtime set to fetch a win32-arm64 Node build.
  • Node version. CI runs Node 22 to match VS Code's Electron, and engines.node is >= 22. runtime: node@22 has to hold that, and CONTRIBUTING's list of files to update when the minimum moves needs this one added.

Baseline

Times from the run on #1110, for comparison after the switch:

Job Setup step, cold store
Unit Test (Linux) 14s
Unit Test (Windows) 69s
Unit Test (Windows ARM64) 2m31s

Pin by SHA, like the other actions. Latest release is v2.1.0.

主要语言
TypeScript
星标
132
派生
48
平均合并
2 天 5 小时
30 天内合并 PR
19

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

coder/vscode-coder 的其他 Issue

查看 coder/vscode-coder 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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