chore: ignore Dependabot patch releases - #1
Conversation
Co-authored-by: Medulla <medulla@tinyhumans.ai>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe Dependabot configuration now ignores patch-version updates for all Cargo and GitHub Actions dependencies. Existing grouping and pull-request limits remain unchanged. ChangesDependabot update filters
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
A rabbit checks the update lane Comment |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1f69f29b3c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| interval: weekly | ||
| ignore: | ||
| - dependency-name: "*" | ||
| update-types: ["version-update:semver-patch"] |
There was a problem hiding this comment.
Keep patch-level security updates enabled
Dependabot applies ignore rules to security updates as well as routine version updates, so this wildcard suppresses a security PR whenever the vulnerability is fixed by a semver-patch release; the identical GitHub Actions rule has the same effect. This contradicts the commit's stated intent that security updates remain unaffected and can leave vulnerable dependencies or actions unpatched, so patch filtering must not be applied through this global ignore rule.
Useful? React with 👍 / 👎.
Tiny Sweeper reviewTiny Sweeper reviewed this change across 6 lane(s) and found 1 active actionable finding(s). Detailed lane evidence and any incomplete work are listed below. State: Ready for maintainer review Review snapshot
Completeness: Complete What changedThe review could not produce a supported behavioral summary; inspect the cited changed surface and lane details below. FeaturesNone identified with supported citations. TestsNo supported feature-to-test mapping was produced. Test execution is not inferred. Findings
Before mergeNone. Agent review detailscritique
security
tests
commits
description
e2e
Evidence and run details
|
There was a problem hiding this comment.
tinysweeper found nothing blocking. Approving.
$0.0010 · 24,266 in / 5,528 out · 12,228 cached (50%) · flash, gpt-5.6-luna, deepseek-v4-flash
critique: $0.0005 · 10,603 in / 1,177 out · 5,072 cached (48%) · gpt-5.6-luna, deepseek-v4-flash
security: $0.0002 · 4,102 in / 213 out · 1,780 cached (43%) · gpt-5.6-luna
description: $0.0001 · 3,623 in / 226 out · 1,024 cached (28%) · deepseek-v4-flash
| directory: / | ||
| schedule: | ||
| interval: weekly | ||
| ignore: |
There was a problem hiding this comment.
Allow routine patch updates
This ignore rule applies to every dependency, so Dependabot will not open any semver-patch updates for this ecosystem. That makes the cargo-minor-and-patch group misleading because its patch updates can never reach the group, and it also suppresses routine GitHub Actions patch updates. Remove these broad ignore rules or narrow them to the specific dependencies that should be excluded.
[RULE] dependency-update-policy ·
Ignore semver patch updates for every configured ecosystem. Minor and major updates remain eligible, and security updates are unaffected.
Summary by CodeRabbit