Skip to content

build(deps): Bump node from 22-slim to 26-slim - #2

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/docker/node-26-slim
Open

build(deps): Bump node from 22-slim to 26-slim#2
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/docker/node-26-slim

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 11, 2026

Copy link
Copy Markdown

Bumps node from 22-slim to 26-slim.

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file docker Pull requests that update docker code labels Jun 11, 2026
@dependabot
dependabot Bot force-pushed the dependabot/docker/node-26-slim branch from 03da4bd to e33e090 Compare June 11, 2026 04:20
@coderabbitai

coderabbitai Bot commented Jun 11, 2026

Copy link
Copy Markdown

Review Change Stack

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d3acec4e-ce69-4792-89a0-9988231e5570

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

The Dockerfile's Stage 1 web-builder image is updated to use Node.js 26-slim instead of Node.js 22-slim for building the Vite SPA frontend assets. No other build stages or runtime configurations were modified.

Changes

Web Builder Base Image

Layer / File(s) Summary
Web builder base image
Dockerfile
Stage 1's FROM directive is updated to use node:26-slim instead of node:22-slim for the web-builder stage that compiles frontend assets.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A node jumps from twenty-two to twenty-six,
Fresh beaver skills in the dependency mix,
The Dockerfile now builds with newer grace,
One line updated, quicker build-time pace!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately and concisely describes the only change: bumping the Node base image from 22-slim to 26-slim.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dependabot/docker/node-26-slim

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.

@coderabbitai coderabbitai 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.

Actionable comments posted: 1

🤖 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.

Inline comments:
In `@Dockerfile`:
- Line 9: Dockerfile's build stage uses "FROM node:26-slim" which conflicts with
CI's node-version "22" and web/package.json's `@types/node` ^22.10.2; update the
Dockerfile's web-builder base image to match the project's Node baseline (e.g.,
change FROM node:26-slim to FROM node:22-slim) or alternatively align CI and
package.json to 26—ensure the chosen Node major version is consistent across
Dockerfile (FROM), .github/workflows/ci.yml (node-version) and web/package.json
(`@types/node`) so all environments use the same Node baseline.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 2c8964ff-b471-49c5-bc49-e5473dc45744

📥 Commits

Reviewing files that changed from the base of the PR and between 7bad9d7 and e33e090.

📒 Files selected for processing (1)
  • Dockerfile

Comment thread Dockerfile

# ---- Stage 1: build the Vite SPA ------------------------------------------
FROM node:22-slim AS web-builder
FROM node:26-slim AS web-builder

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== Dockerfile Node base images =="
rg -n '^\s*FROM\s+node:' Dockerfile

echo
echo "== GitHub workflows node-version settings =="
rg -n 'node-version:\s*"?[0-9]+' .github/workflows

echo
echo "== package.json engines/dev tooling hints =="
fd -a package.json | xargs -I{} sh -c 'echo "--- {}"; rg -n "\"engines\"|`@types/node`|vite|typescript" "{}" || true'

Repository: prateekmulye/FinResearchAI

Length of output: 771


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== Dockerfile Node base images =="
rg -n '^\s*FROM\s+node:' Dockerfile

echo
echo "== GitHub workflows node-version settings =="
rg -n 'node-version:\s*"?[0-9]+' .github/workflows

echo
echo "== package.json engines/dev tooling hints =="
fd -a package.json | xargs -I{} sh -c 'echo "--- {}"; rg -n "\"engines\"|`@types/node`|vite|typescript" "{}" || true'

Repository: prateekmulye/FinResearchAI

Length of output: 771


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== Dockerfile Node base images =="
rg -n '^\s*FROM\s+node:' Dockerfile

echo
echo "== GitHub workflows node-version settings =="
rg -n 'node-version:\s*"?[0-9]+' .github/workflows

echo
echo "== package.json engines/dev tooling hints =="
fd -a package.json | xargs -I{} sh -c 'echo "--- {}"; rg -n "\"engines\"|`@types/node`|vite|typescript" "{}" || true'

Repository: prateekmulye/FinResearchAI

Length of output: 771


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== Dockerfile Node base images =="
rg -n '^\s*FROM\s+node:' Dockerfile

echo
echo "== GitHub workflows node-version settings =="
rg -n 'node-version:\s*"?[0-9]+' .github/workflows

echo
echo "== package.json engines/dev tooling hints =="
fd -a package.json | xargs -I{} sh -c 'echo "--- {}"; rg -n "\"engines\"|`@types/node`|vite|typescript" "{}" || true'

Repository: prateekmulye/FinResearchAI

Length of output: 771


Unify Node version contract between Docker and CI

Dockerfile builds the web-builder stage with FROM node:26-slim, while .github/workflows/ci.yml runs the web job on Node 22 (node-version: "22"). Additionally, web/package.json pins @types/node to ^22.10.2, so CI and Docker are using different Node/type baselines—creating a real validation gap for Node-version-specific issues.

🤖 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` at line 9, Dockerfile's build stage uses "FROM node:26-slim"
which conflicts with CI's node-version "22" and web/package.json's `@types/node`
^22.10.2; update the Dockerfile's web-builder base image to match the project's
Node baseline (e.g., change FROM node:26-slim to FROM node:22-slim) or
alternatively align CI and package.json to 26—ensure the chosen Node major
version is consistent across Dockerfile (FROM), .github/workflows/ci.yml
(node-version) and web/package.json (`@types/node`) so all environments use the
same Node baseline.

Bumps node from 22-slim to 26-slim.

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/docker/node-26-slim branch from e33e090 to 2206a7a Compare July 3, 2026 19:09
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.

0 participants