Skip to content

fix: pnpm 버전을 10.13.1 로 packageManager 핀하여 CI 복구 #141

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
youngminss merged 1 commit into from
May 7, 2026
Merged

fix: pnpm 버전을 10.13.1 로 packageManager 핀하여 CI 복구 #141

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,5 +52,6 @@
"semantic-release": "^24.2.9",
"tailwindcss": "^4",
"typescript": "^5"
}
},
"packageManager": "pnpm@10.13.1"
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot May 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

pnpm v11이 이미 실행되어 pnpm-lock.yaml이 v9으로 업데이트된 경우, packageManager를 v10으로 고정하더라도 lockfile 버전 불일치로 인해 CI 설치 단계에서 오류가 발생할 수 있습니다. CI 복구를 위해 lockfile을 v10 호환 버전(v6 또는 v7)으로 롤백하는 작업이 함께 수행되어야 합니다.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot May 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

packageManager 필드와 더불어 engines 필드에도 pnpm 버전을 명시하는 것을 권장합니다. 이는 Corepack을 사용하지 않는 환경에서도 개발자들이 동일한 pnpm 버전을 사용하도록 유도하여 환경 일관성을 높여줍니다.

	"packageManager": "pnpm@10.13.1",
	"engines": {
		"pnpm": "10.13.1"
	}

}
Loading