chore: upgrade pnpm 9 → 12 di CI, Docker build, dan corepack - #15
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
pnpm 12 (Rust rewrite) memakai format lockfile pnpm 11 yang sama (lockfileVersion '9.0'), jadi --frozen-lockfile tetap valid tanpa regenerasi lockfile. Update pin versi di: - ci.yml dan docker-build.yml (pnpm/action-setup version: 12) - Dockerfile (corepack prepare pnpm@12) - pnpm-workspace.yaml + AGENTS.md (komentar versi) Terverifikasi: pnpm 12.0.0, pnpm install --frozen-lockfile sukses tanpa perubahan lockfile, pnpm test 206/206 pass.
pnpm/action-setup resmi hanya untuk pnpm ≤10; untuk pnpm 11+ (termasuk 12 yang native binary) penggantinya adalah pnpm/setup. Selain itu latest di npm masih menunjuk pnpm 11, jadi pnpm 12 di-install dari dist-tag next-12 (docs resmi pnpm.io/installation#installing-pnpm-12). - ci.yml + docker-build.yml: pnpm/action-setup@v4 + actions/setup-node diganti satu step pnpm/setup@v2 (version: next-12, runtime: node@22, cache: true, install: false — step install --frozen-lockfile tetap eksplisit). setup-node dan corepack enable di runner dihapus. - Dockerfile: corepack prepare pnpm@12 → pnpm@next-12 (corepack 0.29.4+ menerima dist-tag; @pnpm/exe punya varian musl utk Alpine).
anwareset
force-pushed
the
chore/pnpm-12
branch
from
August 29, 2026 03:26
9674591 to
9644594
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ringkasan
Upgrade pnpm dari 9 ke 12 di semua tempat yang mengunci versi pnpm, plus migrasi ke action resmi untuk pnpm 11+.
Perubahan:
.github/workflows/ci.yml+.github/workflows/docker-build.yml—pnpm/action-setup@v4+actions/setup-node@v5diganti satu steppnpm/setup@v2denganversion: next-12,runtime: node@22,cache: true,install: falseDockerfile—corepack prepare pnpm@12→corepack prepare pnpm@next-12pnpm-workspace.yaml+AGENTS.md— komentar versi diperbaruiKenapa pnpm/setup, bukan action-setup?
README resmi
pnpm/action-setup: "This action has a successor: pnpm/setup. For pnpm v11 and newer, use pnpm/setup instead... pnpm/action-setup remains the action to use for installing pnpm v10 and older." pnpm 12 adalah native binary (Rust rewrite) —pnpm/setupmengunduh self-contained binary langsung dari registry, tidak butuh Node.js/npm untuk menginstalnya, dan bisa install runtime (Node) di step yang sama (menggantikanactions/setup-node).Kenapa tag
next-12, bukan12?Dari docs resmi: "latest on npm still points at the pnpm 11 line, so pnpm 12 is installed from the next-12 tag."
latestnpm masih11.24.0, jadi instalasi pnpm 12 memakai dist-tagnext-12. (Semver range12juga resolve ke12.0.0, tapinext-12adalah jalur yang direkomendasikan docs.)Verifikasi
pnpm@next-12→12.0.0(dist-tag valid, terverifikasi vianpm view)corepack prepare pnpm@next-12 --activate→ sukses (exit 0) di corepack 0.29.4 – 0.35.0, termasuk versi yang dibundel Node 22 dinode:22-alpine@pnpm/exe.linux-x64-musl+linux-arm64-musl) untuk AlpinelockfileVersion: '9.0') —pnpm-lock.yamltidak berubahpnpm install --frozen-lockfile(pnpm 12.0.0) → sukses;pnpm test→ 206 pass / 0 failCatatan
install: falsedi pnpm/setup: step eksplisitpnpm install --frozen-lockfiletetap dipertahankan (perilaku deterministik yang sudah ada).