chore(deps): bump the docker-base-images group with 3 updates - #1220
chore(deps): bump the docker-base-images group with 3 updates#1220dependabot[bot] wants to merge 3 commits into
Conversation
Bumps the docker-base-images group with 3 updates: python, node and ollama/ollama. Updates `python` from `b877e50` to `cea0e60` Updates `node` from `ffc7838` to `deae974` Updates `ollama/ollama` from `509fdf5` to `4dea9fb` --- updated-dependencies: - dependency-name: python dependency-version: 3.14-slim dependency-type: direct:production dependency-group: docker-base-images - dependency-name: node dependency-version: 26-slim dependency-type: direct:production dependency-group: docker-base-images - dependency-name: ollama/ollama dependency-version: 4dea9fb511947e24a84237bb636b0203abcb2ff0d3fbc7b4ff865deb91362131 dependency-type: direct:production dependency-group: docker-base-images ... Signed-off-by: dependabot[bot] <support@github.com>
📝 WalkthroughWalkthroughThe Docker build files now use updated SHA256 digests for the Python backend runtime, Node.js frontend builder, and Ollama base image. ChangesContainer image pins
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
Dockerfile.ollama (1)
1-1: 🩺 Stability & Availability | 🔵 TrivialVerify
Dockerfile.ollamain pull-request validation.The supplied workflow snippet lists validation for
Dockerfileandfrontend/Dockerfile, but it does not show aDockerfile.ollamaentry.docker-compose.ymlbuilds this file directly. Confirm that a required check builds this image, validates both model pulls, and runs the resulting image health check. If no check exists, add one before merging this digest update.As per coding guidelines, include the exact focused verification command in the PR body.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@Dockerfile.ollama` at line 1, Verify that pull-request validation includes a required check for Dockerfile.ollama: build the image, validate both model pulls, and run the resulting image health check. If absent, add the check and document the exact focused verification command in the PR body.Source: Coding guidelines
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@Dockerfile.ollama`:
- Line 1: Verify that pull-request validation includes a required check for
Dockerfile.ollama: build the image, validate both model pulls, and run the
resulting image health check. If absent, add the check and document the exact
focused verification command in the PR body.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: e2cdbc0a-0c22-49c0-a30d-4bdff2c0375f
📒 Files selected for processing (2)
DockerfileDockerfile.ollama
|
PR governance metadata gate is not ready for
|
seonghobae
left a comment
There was a problem hiding this comment.
Grouped base-image digest branch refreshed onto live develop. Current head 98e95acd75d14b5009c3baa38ce9a58c2f8db7b9 is zero commits behind and changes only Dockerfile and Dockerfile.ollama. Revalidating current-head build/security checks and independent review.
There was a problem hiding this comment.
Pull request overview
OpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed.
Findings
1. HIGH Current-head GitHub Checks - Fix failed required checks before approval
- Problem: Failed same-head checks remain for
afe54b96821bd3889b43989fa989a667f4847c02. - Root cause: The model-unavailable evidence fallback is allowed only when peer GitHub Checks are complete and clean.
- Fix: Read and fix the failed check logs below, then rerun the current-head checks.
- Regression test: Keep the model-unavailable fallback gated on an empty failed-check rollup.
Failed checks:
- Application CI/backend (Python 3.14): FAILURE (https://github.com/ContextualWisdomLab/naruon/actions/runs/30849364155/job/91805368525)
- backend (Python 3.14) check run: failure (https://github.com/ContextualWisdomLab/naruon/actions/runs/30849364155/job/91805368525)
Changed-File Evidence Map
flowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file (2 files)"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file (2 files)"]
R1 --> V1["required checks"]
OpenCode Review Overview
Pull request overviewOpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed. Findings1. HIGH Current-head GitHub Checks - Fix failed required checks before approval
Failed checks:
Changed-File Evidence Mapflowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file (2 files)"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file (2 files)"]
R1 --> V1["required checks"]
|
|
This digest-only PR is now held as a draft because #1203 is the required superset: it synchronizes all container entry points, derives OCI provenance from the actual first |
|
@dependabot rebase |
|
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
|
Closing as superseded by #1203. This Dependabot branch only changes three raw |
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
Bumps the docker-base-images group with 3 updates: python, node and ollama/ollama.
Updates
pythonfromb877e50tocea0e60Updates
nodefromffc7838todeae974Updates
ollama/ollamafrom509fdf5to4dea9fbDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsSummary by CodeRabbit