Skip to content

Upgrade dependencies#654

Merged
danniel merged 1 commit intomainfrom
feature/upgrade-dependencies
Feb 17, 2026
Merged

Upgrade dependencies#654
danniel merged 1 commit intomainfrom
feature/upgrade-dependencies

Conversation

@danniel
Copy link
Collaborator

@danniel danniel commented Feb 17, 2026

Summary by CodeRabbit

  • Chores
    • Updated Node.js runtime version to 24.13.1 in Docker build configurations for development and production environments.

@coderabbitai
Copy link

coderabbitai bot commented Feb 17, 2026

📝 Walkthrough

Walkthrough

Node.js version is updated from 24.13.0 to 24.13.1 across both production and development Dockerfile configurations. No changes to build steps, runtime environment, or dependencies.

Changes

Cohort / File(s) Summary
Node.js Version Bump
docker/dockerfiles/Dockerfile, docker/dockerfiles/Dockerfile.dev
Updated NODE_VERSION ARG from 24.13.0 to 24.13.1 in both production and development Docker configurations.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • Update node #640: Previous sequential Node.js version bump from 24.12.x to 24.13.0 in the same Dockerfile files.

Poem

🐰 A hop, a skip, and a version bump so fine,
Node 24.13.1 now will shine,
Two Dockerfiles updated with care,
Dependencies fresh as spring air! 🌱

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Upgrade dependencies' is overly broad and generic. While it relates to the changeset, it doesn't clearly identify the specific change: bumping Node.js version from 24.13.0 to 24.13.1 across Dockerfile files. Consider a more specific title like 'Bump Node.js version to 24.13.1' to clearly communicate the primary change and help teammates understand the update at a glance.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feature/upgrade-dependencies

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@docker/dockerfiles/Dockerfile.dev`:
- Line 1: Update the development Dockerfile's Node version argument to match
production by changing the ARG variable NODE_VERSION to the new version value;
locate the ARG NODE_VERSION declaration in docker/dockerfiles/Dockerfile.dev and
set it to the same version used in production (24.13.1) to ensure environment
parity.

@greptile-apps
Copy link

greptile-apps bot commented Feb 17, 2026

Greptile Summary

Routine dependency upgrade bumping Node.js from 24.13.0 to 24.13.1 in both Dockerfiles and updating 14 Python packages to their latest minor/patch versions via uv.lock.

  • Node.js: 24.13.0 → 24.13.1 in both Dockerfile and Dockerfile.dev
  • Python dependencies (all minor/patch bumps within pyproject.toml ~= constraints): boto3/botocore 1.42.43→1.42.50, cryptography 46.0.4→46.0.5, django-allauth 65.14.0→65.14.3, django-environ 0.12.0→0.12.1, phonenumbers 9.0.23→9.0.24, reportlab 4.4.9→4.4.10, faker 40.1.2→40.1.3, coverage 7.13.3→7.13.4, pillow 12.1.0→12.1.1
  • Transitive dependencies: filelock 3.20.3→3.24.2, platformdirs 4.5.1→4.9.2, virtualenv 20.36.1→20.37.0, wcwidth 0.5.3→0.6.0
  • No packages were added or removed; no pyproject.toml changes were made
  • Node.js version is consistent across both Dockerfiles

Confidence Score: 5/5

  • This PR is safe to merge — it contains only routine minor/patch dependency version bumps with no code changes.
  • All changes are lock file version bumps and a Node.js patch version increment. No application code is modified, no packages are added or removed, and all updates stay within the declared version constraints in pyproject.toml. The risk of regression is minimal.
  • No files require special attention.

Important Files Changed

Filename Overview
docker/dockerfiles/Dockerfile Node.js version bumped from 24.13.0 to 24.13.1 (patch update). No other changes.
docker/dockerfiles/Dockerfile.dev Node.js version bumped from 24.13.0 to 24.13.1 (patch update), consistent with production Dockerfile.
backend/uv.lock Lock file updated with minor/patch bumps for 14 packages (both direct and transitive). No packages added or removed. All versions remain within pyproject.toml constraints.

Flowchart

flowchart TD
    A["pyproject.toml\n(version constraints unchanged)"] --> B["uv.lock\n(14 packages bumped)"]
    B --> C["Direct Dependencies"]
    B --> D["Transitive Dependencies"]
    C --> C1["boto3/botocore 1.42.43→1.42.50"]
    C --> C2["cryptography 46.0.4→46.0.5"]
    C --> C3["django-allauth 65.14.0→65.14.3"]
    C --> C4["django-environ 0.12.0→0.12.1"]
    C --> C5["phonenumbers 9.0.23→9.0.24"]
    C --> C6["reportlab 4.4.9→4.4.10"]
    C --> C7["faker 40.1.2→40.1.3"]
    C --> C8["coverage 7.13.3→7.13.4"]
    C --> C9["pillow 12.1.0→12.1.1"]
    D --> D1["filelock 3.20.3→3.24.2"]
    D --> D2["platformdirs 4.5.1→4.9.2"]
    D --> D3["virtualenv 20.36.1→20.37.0"]
    D --> D4["wcwidth 0.5.3→0.6.0"]
    E["Dockerfile + Dockerfile.dev"] --> F["Node.js 24.13.0→24.13.1"]
Loading

Last reviewed commit: 9db390d

@danniel danniel merged commit 92503c6 into main Feb 17, 2026
10 checks passed
@danniel danniel deleted the feature/upgrade-dependencies branch February 17, 2026 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant