upgrade deps and node version

[dinmukhamedm]

Update transitive dependencies to fix most dependabot issues

---

Important

Update dependencies and Node.js version to address dependabot issues, including changes to Cargo.lock, Cargo.toml, Dockerfile, and package.json.

• Dependencies:
  • Update actix-web to 4.11 in Cargo.toml.
  • Update Node.js base image to 24-alpine in Dockerfile.
  • Update various dependencies in package.json, including @ai-sdk/*, @aws-sdk/client-s3, @clickhouse/client, @radix-ui/*, next, react, and others.
• Removals:
  • Remove route.ts file from frontend/app/api/projects/[projectId]/images/[imageId]/.
• Misc:
  • Update Cargo.lock with new dependency versions for Rust packages.

^{This description was created by for 214df7a. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 214df7a in 1 minute and 39 seconds. Click for details.

• Reviewed 3744 lines of code in 5 files
• Skipped 1 files when reviewing.
• Skipped posting 5 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. app-server/Cargo.toml:2

• Draft comment:
  The package edition is set to '2024'. Ensure that your toolchain, linter, and CI support this future edition to avoid unexpected build issues.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. frontend/Dockerfile:11

• Draft comment:
  The Dockerfile installs dependencies using pnpm (via 'yarn global add pnpm' and 'pnpm i') but later runs the build with 'npm run build'. Using different package managers in one image can lead to inconsistencies. Consider using the same package manager consistently.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

3. frontend/package.json:103

• Draft comment:
  The 'react' and 'react-dom' versions are set to '^19.1.1', which is unusual given that the stable React release is typically in the 18.x range. Please confirm if this upgrade is intentional, as it may lead to compatibility issues with Next.js or other libraries.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50% This is a dependency version change. According to our rules, we should NOT comment on dependency changes or library versions we don't recognize. The PR author likely has a good reason for using React 19, and dependency management is their responsibility. Additionally, the build system would catch any actual compatibility issues. The comment raises a valid concern about potential compatibility issues, which could be a real problem if React 19 is unstable or experimental. While the concern is valid, our rules explicitly state not to comment on dependency changes or library versions. Build/test systems will catch real compatibility problems. Delete this comment as it violates our rule about not commenting on dependency changes or library versions.

4. app-server/Cargo.lock:5493

• Draft comment:
  Typographical error: The package name 'wasite' appears to be a typo. If the intent was to reference the 'wasi' package, please correct it.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

5. app-server/Cargo.lock:5838

• Draft comment:
  Typographical note: The package name "windows_aarch64_gnullvm" looks unusual and might be a misspelling. Please verify if it should be, for example, "windows_aarch64_gnu" or otherwise corrected to match consistent naming conventions.
• Reason this comment was not posted:
  Comment was on unchanged code.

Workflow ID: wflow_RdfpqjWAGLST3wW2

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}