build(deps): bump node from 24-bookworm-slim to 26-bookworm-slim

[dependabot]

Bumps node from 24-bookworm-slim to 26-bookworm-slim.

[coderabbitai]

📝 Walkthrough

Walkthrough

The Dockerfile now uses Node.js 26 with Debian bookworm slim for both build and runtime stages.

Changes

Container runtime

Layer / File(s)	Summary
Update Docker image stages Dockerfile	The build and runtime stages now use node:26-bookworm-slim instead of Node.js 24.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: jusso-dev

🚥 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 summarizes the main change: bumping the Docker base image from Node 24 bookworm slim to Node 26 bookworm slim.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dependabot/docker/node-26-bookworm-slim

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

Dockerfile (1)

1-1: 🩺 Stability & Availability | 🔵 Trivial | ⚡ Quick win

Add Node.js 26 container coverage to CI.

The Docker stages now build and run under Node.js 26, while the supplied CI and security workflows still execute on Node.js 24. Add a Docker build/smoke test or update the relevant workflow jobs so Node.js 26-specific regressions are exercised before release.

Also applies to: 10-10

🤖 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 1, Update the relevant CI and security workflow jobs to
exercise Node.js 26, matching the Dockerfile’s node:26-bookworm-slim build and
runtime stages. Add a Docker build/smoke test or otherwise ensure the workflows
validate Node.js 26-specific behavior before release, including the
corresponding configuration at the referenced secondary location.

🤖 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 1: Update both Dockerfile stages around the existing corepack enable
steps to install Corepack or pnpm before invoking corepack enable, ensuring the
Node.js 26 image can execute the package-manager setup successfully.

---

Nitpick comments:
In `@Dockerfile`:
- Line 1: Update the relevant CI and security workflow jobs to exercise Node.js
26, matching the Dockerfile’s node:26-bookworm-slim build and runtime stages.
Add a Docker build/smoke test or otherwise ensure the workflows validate Node.js
26-specific behavior before release, including the corresponding configuration
at the referenced secondary location.

🪄 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: 56fe8bd4-0452-401f-a393-ff010ad60957

📥 Commits

Reviewing files that changed from the base of the PR and between efbc2ff and ceb435e.

📒 Files selected for processing (1)

• Dockerfile

[coderabbitai]

🩺 Stability & Availability | 🔴 Critical | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/sh
set -eu
docker run --rm node:26-bookworm-slim sh -lc 'command -v corepack'

Repository: jusso-dev/Muster

Length of output: 198

---

🏁 Script executed:

#!/bin/sh
set -eu

printf '\n== Dockerfile ==\n'
cat -n Dockerfile

printf '\n== CI / workflow files mentioning node ==\n'
git ls-files '.github/**' | while IFS= read -r f; do
  grep -nE 'node:|actions/setup-node|corepack|pnpm' "$f" || true
done

Repository: jusso-dev/Muster

Length of output: 2162

---

🌐 Web query:

Node.js 26 corepack bundled removed node 25 documentation corepack executable not included

💡 Result:

Corepack is no longer bundled with Node.js starting from version 25.0.0 [1][2]. The Node.js Technical Steering Committee decided to stop distributing the Corepack executable in Node.js 25+ releases, ending a period where it was distributed with Node.js versions 14.19.0 and 16.9.0 through 24.x [1][3]. If you were previously relying on the bundled corepack executable, you can continue using Corepack by installing it as a userland package via npm [1][4]. You can install it globally by running: npm install -g corepack@latest This command provides the same corepack functionality that was previously included in the Node.js distribution [5][4]. Node.js documentation has been updated to reflect this change and to direct users to the Corepack repository for installation instructions [1][6].

Citations:

• 1: https://nodejs.org/dist/latest/docs/api/corepack.html
• 2: https://github.com/nodejs/nodejs.org/blob/main/apps/site/pages/en/blog/release/v25.0.0.md
• 3: doc: note corepack package removal in distribution doc nodejs/node#61207
• 4: deps: remove corepack nodejs/node#51981
• 5: https://github.com/nodejs/corepack?tab=readme-ov-file
• 6: nodejs/node@570d8d3f10

---

Install Corepack before corepack enable. Node.js 26 no longer ships the bundled corepack binary, so the corepack enable steps in both stages will fail unless Corepack or pnpm is installed first.

🤖 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 1, Update both Dockerfile stages around the existing
corepack enable steps to install Corepack or pnpm before invoking corepack
enable, ensuring the Node.js 26 image can execute the package-manager setup
successfully.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.