Skip to content

ci: gha-security のセキュリティチェック導入 + digest固定 + cooldown(パイロット)#2

Open
kaitoyama wants to merge 2 commits into
mainfrom
gha-security-pilot
Open

ci: gha-security のセキュリティチェック導入 + digest固定 + cooldown(パイロット)#2
kaitoyama wants to merge 2 commits into
mainfrom
gha-security-pilot

Conversation

@kaitoyama

Copy link
Copy Markdown
Collaborator

traPtitech/gha-security のパイロット導入です。Checkin は「bot 未導入のリポジトリにフルセットを入れる」確認役で、pin と cooldown の両方をこの PR だけで完結させています。

変更内容

ファイル 内容
.github/workflows/security-checks.yaml PR 時のチェック: pin-support(未固定参照の修正を suggestion で提案)/ pin-check(未固定があれば fail)/ cooldown-check(公開から日が浅い依存バージョンの混入で fail。npm 7日・actions 3日)
docker-compose.yml mariadb:11@sha256: digest を付与(gha-security の pin-docker による自動生成)
.github/dependabot.yml actions の SHA / docker の digest / npm を週次で自動追従(cooldown 付き。セキュリティ修正は cooldown をバイパスして即時)
pnpm-workspace.yaml minimumReleaseAge: 10080(7日)— 手元の pnpm add でも公開直後のバージョンが解決されなくなります(@traptitech/* は除外)

補足

  • actions 3件は既に SHA 固定済みだったのでそのままです
  • 緊急で新しいバージョンが必要な場合: PR に cooldown-override ラベル(CI 側)、pnpm add は一時的に --config.minimumReleaseAge=0(手元側)
  • 各機能は独立してオン/オフできます(gha-security README 参照)。運用に合わなければジョブ削除や設定変更で調整してください

🤖 Generated with Claude Code

- security-checks.yaml: pin-support / pin-check / cooldown-check (PR 時)
- docker-compose.yml: mariadb:11 を digest 固定 (以後 Dependabot が追従)
- dependabot.yml: github-actions / docker / npm を cooldown 付きで自動更新
- pnpm-workspace.yaml: minimumReleaseAge 7日 (手元 install にも cooldown)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 44 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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4947c147-80be-47a3-ace5-b27fbf7c7241

📥 Commits

Reviewing files that changed from the base of the PR and between 770079a and f175447.

📒 Files selected for processing (4)
  • .github/dependabot.yml
  • .github/workflows/security-checks.yaml
  • docker-compose.yml
  • pnpm-workspace.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch gha-security-pilot

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.

1 participant