Skip to content

fix(npm): package.json에 repository URL 추가하여 publish 실패 복구#53

Merged
4entrepreneur merged 1 commit into
mainfrom
hy/fix-npm-publish-repo-url
May 5, 2026
Merged

fix(npm): package.json에 repository URL 추가하여 publish 실패 복구#53
4entrepreneur merged 1 commit into
mainfrom
hy/fix-npm-publish-repo-url

Conversation

@4entrepreneur

Copy link
Copy Markdown
Collaborator

Summary

  • npm publish --provenance가 v0.4.0/v0.4.1 릴리스에서 422 Unprocessable Entity로 실패하던 원인 수정
  • package.jsonrepository.url (+ homepage, bugs) 필드를 추가해 sigstore provenance bundle의 GitHub repo URL과 npm registry 검증이 일치하도록 함

Why

워크플로우 로그(run 25327439005):

```
422 Unprocessable Entity - PUT https://registry.npmjs.org/@openclone%2fopenclone
Failed to validate repository information:
package.json: "repository.url" is "", expected to match
"https://github.com/open-clone/openclone" from provenance
```

이 실패 때문에 npm 레지스트리 최신 버전이 아직 `0.3.0` (2026-04-29)이고, 그 이후 머지된 PR들(#46/#48/#49/#47/#50/#51/#52)이 npm 사용자에게 도달하지 못한 상태.

`version` 필드는 손대지 않음. publish 워크플로우의 `Stamp package version from release tag` 단계가 release tag로부터 자동으로 박음.

Test plan

🤖 Generated with Claude Code

publish-npm 워크플로우가 v0.4.0/v0.4.1에서 422로 실패하던 원인.
sigstore provenance가 GitHub repo URL을 박는데 package.json의
repository.url이 비어 있어 npm registry 매칭 검증에서 거부됨.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@vkehfdl1

vkehfdl1 commented May 5, 2026

Copy link
Copy Markdown
Collaborator

Thanks for the contribution! 🙏

This repository's automation only reviews pull requests that target the dev branch (this PR currently targets main). Please change the base branch to dev so dani can pick it up for automated review.

GitHub UI → click "Edit" next to the PR title → change the base branch to dev, then push (or reopen) the PR.

@4entrepreneur
4entrepreneur merged commit d040309 into main May 5, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants