chore: update node version docker

[AndrewHanasiro]

Summary by CodeRabbit

• Chores
  • Updated the containerized runtime environment to a more recent Node.js version for improved stability and security
  • Application is now configured to expose port 5000 for external access

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The Dockerfile has been updated to use Node.js version 24.11.1-trixie-slim across all multi-stage build phases, replacing version 24.10.0-slim. In the final deploy stage, package.json is now copied into the image and port 5000 is explicitly exposed.

Changes

Cohort / File(s)	Summary
Docker configuration Dockerfile	Updated Node.js base image from 24.10.0-slim to 24.11.1-trixie-slim in dependency, builder, and deploy stages; added package.json copy and port 5000 exposure in deploy stage

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Verify base image version compatibility with application requirements
• Confirm package.json copy location aligns with intended structure in deploy stage
• Validate port 5000 exposure matches application configuration

Poem

🐰 A hop through the Node-ular realm we go,
From 24.10 to 24.11, watch it flow,
Package files bundled, port exposed so bright,
Container builds faster, everything's right! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request has no description, missing the required Proposal and Links sections from the repository template.	Add a pull request description following the repository template, including a Proposal section explaining the rationale for the Node.js version update and relevant Links.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: updating Node.js version in Docker configuration from 24.10.0 to 24.11.1.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch hotfix/snyk

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c5c510e and e42054f.

📒 Files selected for processing (1)

• Dockerfile (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Codacy Static Code Analysis

🔇 Additional comments (1)

Dockerfile (1)

1-1: Node.js security patch is appropriate and verified.

The base image has been correctly updated from node:24.10.0-slim to node:24.11.1-trixie-slim across all three stages. Version 24.10.0 bundles OpenSSL 3.5.3, which is affected by CVE-2025-9230 (out-of-bounds read/write in RFC3211 KEK Unwrap). Version 24.11.1 addresses this vulnerability and includes the OpenSSL 3.5.4+ fix. The explicit -trixie-slim tag improves reproducibility. No further action needed on this change.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud