chore: ignore Dependabot patch releases - #34
Conversation
Co-authored-by: Medulla <medulla@tinyhumans.ai>
|
Warning Review paused — included plan limit reachedKeep your review moving with free on-demand reviews.
On-demand reviews are free for one more day. Promotion and pricing detailsOn-demand reviews are free for one more day. After that, they cost $0.25 per reviewed file. Review limit detailsOr wait 13 seconds for your next included review. Limit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
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: 2a0a946106
ℹ️ 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".
| ignore: | ||
| - dependency-name: "*" | ||
| update-types: ["version-update:semver-patch"] |
There was a problem hiding this comment.
Preserve patch-level security updates
When an advisory is fixed by a patch release, Dependabot security updates honor ignore rules, so this wildcard suppresses the remediation PR rather than only routine version-update noise; the identical GitHub Actions rule has the same problem. This contradicts the commit's stated expectation that security updates remain unaffected and can leave a vulnerable locked dependency without an automated fix, so routine patch PRs need to be filtered by a mechanism that does not globally ignore patch updates.
Useful? React with 👍 / 👎.
Tiny Sweeper reviewTiny Sweeper reviewed this change across 6 lane(s) and found 3 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.0030 · 56,255 in / 6,119 out · 7,876 cached (14%) · ladder/vectors, gpt-5.6-luna, deepseek-v4-flash · 34 embedded
critique: $0.0018 · 32,751 in / 2,261 out · 5,072 cached (15%) · gpt-5.6-luna, deepseek-v4-flash
security: $0.0009 · 15,165 in / 846 out · 1,780 cached (12%) · gpt-5.6-luna
description: $0.0001 · 6,758 in / 687 out · 1,024 cached (15%) · deepseek-v4-flash
| directory: / | ||
| schedule: | ||
| interval: weekly | ||
| ignore: |
There was a problem hiding this comment.
Keep patch updates enabled for GitHub Actions
This rule also applies to the GitHub Actions update group, preventing automatic patch updates for every action. That can leave workflow actions on versions with known or subsequently fixed vulnerabilities and delays security maintenance across CI. Remove the wildcard suppression or narrowly exclude only actions with a demonstrated incompatibility.
Additional critique observation
Allow grouped Cargo patch updates
[RULE] dependency-update-scope
This wildcard ignore takes precedence over the cargo-minor-and-patch group below, so the group can receive minor updates but never patch updates. For example, a dependency update from 0.13.1 to 0.13.2 will be suppressed entirely, including fixes delivered in patch releases, contradicting the existing group configuration and the repository's stated Dependabot practice. Remove this ignore entry or narrow it to dependencies that are intentionally excluded.
Suggested change for this observation (reference only)
Additional security observation
Do not suppress patch updates for every dependency
[RULE] dependency-update-suppression
The wildcard ignore rule disables routine patch updates for every Cargo dependency in this update group, including patches that may contain security fixes or important bug fixes. Dependabot's separate security-update flow can cover known advisories, but fixes that are not yet recognized as advisories—or updates needed to keep the dependency graph secure—will no longer be proposed automatically. Remove the wildcard suppression or scope it to specific dependencies with a documented compatibility reason.
[RULE] dependency-update-suppression ·
Ignore semver patch updates for every configured ecosystem. Minor and major updates remain eligible, and security updates are unaffected.