fix(ci): release checkout는 기본 GITHUB_TOKEN 사용 + fetch-depth/token 제거#151
Merged
Conversation
…n에만 주입 checkout이 봇 PAT로 git fetch를 시도하다 'could not read Username'(exit 128)으로 실패. checkout은 레포 read만 필요하므로 기본 GITHUB_TOKEN으로 충분하고, 봇 PAT(GH_TOSSPAYMENTS_BOT_TOKEN)는 PR 생성이 필요한 changesets/action에만 둔다. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
changesets/action은 changeset 파일과 npm 레지스트리 비교로 동작해 전체 git 히스토리가 불필요. 기본 depth로 충분. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
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.
문제
PR #150 머지 후 Release 워크플로우가 checkout에서 실패:
actions/checkout에 봇 PAT(GH_TOSSPAYMENTS_BOT_TOKEN)를token으로 주입했는데, 그 PAT로 git fetch가 거부됨.수정
checkout은 레포 read만 필요 → 기본GITHUB_TOKEN사용 (커스텀token입력 제거)changesets/action에만 유지fetch-depth: 0제거 — changesets는 changeset 파일 + npm 레지스트리 비교로 동작하므로 전체 git 히스토리 불필요 (기본 depth로 충분)효과
changeset publish는 no-op이라 greenchangesets/action이 봇 PAT로 PR을 만들어 CI를 트리거 — 이때 PAT는 Contents: RW + Pull requests: RW (+ org SSO 승인) 가 필요🤖 Generated with Claude Code