Skip to content

ci: npm 배포 셋업 (publishConfig·릴리스 워크플로) - #12

Merged
jeongph merged 1 commit into
mainfrom
feature/npm-publish
Jul 24, 2026
Merged

ci: npm 배포 셋업 (publishConfig·릴리스 워크플로)#12
jeongph merged 1 commit into
mainfrom
feature/npm-publish

Conversation

@jeongph

@jeongph jeongph commented Jul 24, 2026

Copy link
Copy Markdown
Member

@followingseas/pilot을 npm에 배포 가능하게 셋업한다. Closes #10 (코드/설정 부분).

변경

  • package.json
    • 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.

배포하려면 (사용자 계정 작업 — 내가 못 하는 부분)

  1. npm에 followingseas 조직 생성 (또는 개인 스코프)
  2. npm automation token 발급 → 이 repo Settings → Secrets → NPM_TOKEN 등록
  3. 버전 태그 후 GitHub Release publish → 워크플로가 자동 배포
    • 첫 배포는 로컬에서 npm publish 한 번 해도 됨 (prepublishOnly가 빌드)

배포되면 npm i -g @followingseas/pilot로 실제 설치 → wake 재검증 가능.

🤖 Generated with Claude Code

@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@jeongph, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 12 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a83beaa9-2e8d-4993-b6db-5ec57f28cc2a

📥 Commits

Reviewing files that changed from the base of the PR and between f468fb7 and f2f85b3.

📒 Files selected for processing (2)
  • .github/workflows/publish.yml
  • package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feature/npm-publish

Comment @coderabbitai help to get the list of available commands.

@jeongph
jeongph merged commit 2d6481e into main Jul 24, 2026
2 checks passed
@jeongph
jeongph deleted the feature/npm-publish branch July 24, 2026 16:47
@jeongph jeongph self-assigned this Jul 26, 2026
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.

pilot npm 정식 배포 (@followingseas/pilot)

1 participant