ci: npm 배포 셋업 (publishConfig·릴리스 워크플로) - #12
Conversation
|
Warning Review limit reached
Next review available in: 12 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
@followingseas/pilot을 npm에 배포 가능하게 셋업한다. Closes #10 (코드/설정 부분).변경
publishConfig: { access: public }— 스코프 패키지 공개 배포prepublishOnly: npm run build— 배포 전 빌드 보장keywords채움.github/workflows/publish.yml— GitHub Release publish 시npm publish --provenance(OIDC 공급망 보안)로 자동 배포검증
npm pack --dry-run: tarball에dist/**·README·LICENSE·package.json만 6개 (src/tests 제외 확인), 27.8kB.배포하려면 (사용자 계정 작업 — 내가 못 하는 부분)
followingseas조직 생성 (또는 개인 스코프)NPM_TOKEN등록npm publish한 번 해도 됨 (prepublishOnly가 빌드)배포되면
npm i -g @followingseas/pilot로 실제 설치 → wake 재검증 가능.🤖 Generated with Claude Code