fix: pnpm-lock.yaml tinyglobby@0.2.17 중복 키 제거 (CI 수정)#81
Merged
Conversation
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
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 #80 (dependabot
actions/checkoutv6→v7)에서 CI가 실패한 진짜 원인은actions/checkout버전이 아니라pnpm-lock.yaml의 YAML duplicated mapping key였습니다.packages섹션:tinyglobby@0.2.17이 두 번 선언됨snapshots섹션:tinyglobby@0.2.17이 두 번 선언됨이 broken lockfile은
develop브랜치에 이미 존재했으나, CI trigger가push: [main]만 포함되어 발견되지 않았습니다. dependabot PR이 develop 타겟 PR을 트리거해 처음으로 드러남.수정 내용
pnpm-lock.yamlpackages 섹션에서tinyglobby@0.2.17중복 항목 제거pnpm-lock.yamlsnapshots 섹션에서tinyglobby@0.2.17중복 항목 제거다음 조치
이 PR 머지 후 PR #80 재실행하면 CI 통과 가능.