Skip to content

chore: supply-chain & deployment hygiene (#113, #91, #67, #65, #60, #72, #90) - #124

Merged
Liohtml merged 1 commit into
mainfrom
claude/dependabot-maintenance-u1mdmh
Jul 2, 2026
Merged

chore: supply-chain & deployment hygiene (#113, #91, #67, #65, #60, #72, #90)#124
Liohtml merged 1 commit into
mainfrom
claude/dependabot-maintenance-u1mdmh

Conversation

@Liohtml

@Liohtml Liohtml commented Jul 2, 2026

Copy link
Copy Markdown
Owner

Third batch of repo-health fixes, focused on supply-chain and deployment hygiene:

Closes #113, closes #91, closes #67, closes #65, closes #60, closes #72, closes #90.

🤖 Generated with Claude Code

https://claude.ai/code/session_014ywk8AWq5mgbeERmvuhcJy


Generated by Claude Code

- Pin github/codeql-action to a full commit SHA instead of the mutable
  v4 tag (#113)
- Remove the global bandit B104 skip; the scan is clean without it (#91)
- Pin uv in the Dockerfile to 0.8.17 instead of :latest for
  reproducible builds (#67)
- Mount ./data read-only in docker-compose (#65)
- Commit uv.lock and stop gitignoring it so builds are reproducible
  (#60, #72)
- Fix stale Claude model reference in .env.example (#90)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014ywk8AWq5mgbeERmvuhcJy
@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 51 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: bd9405a2-6c4d-42c8-80c1-b8cc2f832449

📥 Commits

Reviewing files that changed from the base of the PR and between ed0b905 and 521e668.

⛔ Files ignored due to path filters (1)
  • uv.lock is excluded by !**/*.lock
📒 Files selected for processing (6)
  • .env.example
  • .github/workflows/codeql.yml
  • .gitignore
  • Dockerfile
  • docker-compose.yml
  • pyproject.toml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/dependabot-maintenance-u1mdmh

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.

@codecov

codecov Bot commented Jul 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment