Skip to content

build(deps): bump node from 20-bookworm-slim to 25-bookworm-slim in /packages/orchestration/skills/dev-tools/multi-model-review/sandbox - #74

Open
dependabot[bot] wants to merge 35 commits into
mainfrom
dependabot/docker/packages/orchestration/skills/dev-tools/multi-model-review/sandbox/node-25-bookworm-slim
Open

build(deps): bump node from 20-bookworm-slim to 25-bookworm-slim in /packages/orchestration/skills/dev-tools/multi-model-review/sandbox#74
dependabot[bot] wants to merge 35 commits into
mainfrom
dependabot/docker/packages/orchestration/skills/dev-tools/multi-model-review/sandbox/node-25-bookworm-slim

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 31, 2026

Copy link
Copy Markdown

Bumps node from 20-bookworm-slim to 25-bookworm-slim.

Dependabot compatibility score

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

…iation

Remediate local Codacy findings and restore verification
…iation

Add local graph memory and complete Codacy remediation
Publish a GitHub Pages demo derived from the canonical operator UI, backed only by sanitized in-memory fixtures and visibly simulated command actions.
…lows

Add graph-native workflows and bounded policy improvement
…-complexity

Simplify workflow collect policy guard
sebastianspicker and others added 5 commits July 31, 2026 09:03
Bumps node from 20-bookworm-slim to 25-bookworm-slim.

---
updated-dependencies:
- dependency-name: node
  dependency-version: 25-bookworm-slim
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file docker Pull requests that update docker code labels Jul 31, 2026
@dependabot
dependabot Bot requested a review from sebastianspicker as a code owner July 31, 2026 17:14
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file docker Pull requests that update docker code labels Jul 31, 2026
@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

Run reviewer

TIP This summary will be updated as you push new changes.

@codacy-production codacy-production Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

While Codacy reports the PR as up to standards, the Dockerfile contains a critical path mismatch that will prevent successful image construction. The build artifacts are generated in a directory that does not match the paths used in the runner stage's copy commands. Additionally, the PR fails to meet the acceptance criterion requiring the use of SHA256 digests for image immutability. These issues should be resolved before merging.

Test suggestions

  • Verify successful Docker image build using Node 25 and npm ci
  • Verify application entrypoint (node dist/index.js) execution on Node 25
  • Verify Docker healthcheck command passes on Node 25
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify successful Docker image build using Node 25 and npm ci
2. Verify application entrypoint (node dist/index.js) execution on Node 25
3. Verify Docker healthcheck command passes on Node 25

TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback

@@ -1,12 +1,12 @@
# Build a hermetic review-skill image so validation does not depend on host tooling.
FROM node:20-bookworm-slim@sha256:2cf067cfed83d5ea958367df9f966191a942351a2df77d6f0193e162b5febfc0 AS build
FROM node:25-bookworm-slim@sha256:81db02c4b671288a03915da9534dbd54f96d0e7c24d80ccc54f5b36b2e684370 AS build

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴 HIGH RISK

The build stage WORKDIR is set to /skill (line 3), but the runner stage attempts to copy artifacts from /workspace/_shared/ and /workspace/multi-model-review/ (lines 12-16). This discrepancy will cause the build to fail because the artifacts produced in /skill will not exist at the expected /workspace paths. Try running the following prompt in your coding agent: Fix the Dockerfile to use consistent paths by setting the build stage WORKDIR to /workspace/multi-model-review and ensuring all required components are correctly copied and built.

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

Labels

dependencies Pull requests that update a dependency file docker Pull requests that update docker code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant