update dockerfile node 22

[giurgiur99]

Fixes # .

Changes proposed in this PR:

[alexcos20]

AI automated code review (Gemini 3).

Overall risk: medium

Summary:
This pull request updates the Node.js version used in the Dockerfile from v20.19.0 to v22.5.1. This is a major version upgrade for Node.js, which can potentially introduce breaking changes or compatibility issues with existing dependencies and application code.

Comments:
• [WARNING][other] Updating the Node.js version from v20 (LTS) to v22 (Current) is a significant change. Node.js v22 introduces new features and potential breaking changes that could affect application stability or dependency compatibility.

Could you please confirm the following:

1. Has the application been thoroughly tested with Node.js v22.5.1? Are there any known compatibility issues?
2. Are all direct and indirect dependencies compatible with Node.js v22?
3. Is there a specific reason for moving to Node.js v22 (Current release) rather than staying on Node.js v20 (LTS) or waiting for v22 to become an LTS release (scheduled for October 2024)? While staying updated is good, major version bumps often require more rigorous testing.

Please ensure that the CI/CD pipeline includes tests that validate functionality against this new Node.js version.

[alexcos20]

AI automated code review (Gemini 3).

Overall risk: medium

Summary:
This pull request updates the Node.js version in the Dockerfile from v20.19.0 (LTS) to v22.5.1 (Current release).

Comments:
• [WARNING][other] The Node.js version is being updated from v20.19.0 to v22.5.1. While upgrading is generally good for security and performance, Node.js 22 is currently the 'Current' release, not an 'LTS' (Long Term Support) version. Node.js 20 is an active LTS release.

For production environments, it is typically recommended to stick to LTS versions for enhanced stability and predictable support cycles. Could you please provide the rationale for moving to Node.js 22 at this stage? Have all project dependencies been verified for full compatibility with Node.js 22? Please confirm that thorough testing (unit, integration, and manual) has been performed with this new Node.js version to ensure no regressions or unexpected behaviors are introduced.

[alexcos20]

AI automated code review (Gemini 3).

Overall risk: medium

Summary:
This pull request updates the Node.js version used in the Dockerfile from v20.19.0 to v22.5.1. This is a major version upgrade from Node.js 20 (LTS) to Node.js 22 (Current).

Comments:
• [WARNING][other] This PR updates the Node.js version from v20.19.0 to v22.5.1. This is a major version upgrade which could introduce breaking changes or compatibility issues, even though v22.5.1 is a patch release within the Node.js 22 series.

Please confirm that comprehensive testing has been performed with Node.js v22.5.1 to ensure the application and all its functionalities operate correctly within this new environment. It would also be helpful to understand the primary motivation for this upgrade (e.g., security patches, performance improvements, new language features, or preparing for Node.js 22 LTS).

[alexcos20]

AI automated code review (Gemini 3).

Overall risk: medium

Summary:
This pull request updates the Node.js version in the Dockerfile from v20.19.0 to v22.5.1. This is a major version bump for Node.js.

Comments:
• [WARNING][other] The Node.js version is being updated from v20.19.0 (LTS) to v22.5.1 (Current). This is a significant major version upgrade. Have we thoroughly tested the ocean-node application with Node.js 22.x to ensure there are no breaking changes or unexpected behaviors introduced by this update? Please confirm the rationale for moving to Node.js 22.x at this time and that compatibility testing has been completed.

[alexcos20]

AI automated code review (Gemini 3).

Overall risk: medium

Summary:
This pull request updates the Node.js version in the Dockerfile from v20.19.0 to v22.5.1. This is a major version bump and moves from a Long Term Support (LTS) release to a 'Current' release. While Node.js v22 is slated to become LTS in October 2024, it is not an LTS release at this moment. Such an upgrade requires careful verification of all dependencies and application functionality to ensure compatibility and stability.

Comments:
• [WARNING][other] The Node.js version is being updated from v20.19.0 (an LTS release) to v22.5.1 (a 'Current' release). While Node.js v22 will eventually be LTS, it is not yet. This transition can potentially introduce breaking changes or compatibility issues with existing project dependencies. Please ensure that comprehensive testing (unit, integration, and end-to-end) is performed to validate the application's functionality and stability on this new Node.js version. It would be beneficial to document the reasoning for moving to a non-LTS version at this time.

[alexcos20]

AI automated code review (Gemini 3).

Overall risk: medium

Summary:
This pull request updates the Node.js version used in the Dockerfile from v20.19.0 to v22.5.1. This constitutes an upgrade from an Active LTS release (Node.js 20) to the current stable release (Node.js 22), which is slated to become the next LTS version.

Comments:
• [WARNING][other] The Node.js version is being updated from v20.19.0 (Active LTS) to v22.5.1 (Current release). While updating to newer versions is generally good practice, a major version bump like this can introduce breaking changes or require updates to application dependencies. Please confirm that the application has been thoroughly tested for full compatibility with Node.js 22.x, and that any potential regressions or performance impacts have been evaluated.

[alexcos20]

AI automated code review (Gemini 3).

Overall risk: medium

Summary:
This pull request updates the Node.js version in the Dockerfile from v20.19.0 to v22.15.0. Moving to a newer LTS version is generally beneficial for security, performance, and access to modern language features. However, a major version upgrade of Node.js can introduce compatibility issues that require thorough testing.

Comments:
• [WARNING][bug] Upgrading Node.js from v20 to v22 is a major version jump, even within LTS lines. While generally positive for performance and security, it's crucial to verify that all existing dependencies and application code are fully compatible with Node.js v22. Please ensure that all unit, integration, and end-to-end tests pass successfully with this new Node.js version. If possible, a dedicated test run or CI job for this Node.js version prior to merge would be ideal.
• [INFO][other] It's great to keep the Node.js version updated. For future reference, consider adding a comment near this line or in project documentation regarding the chosen Node.js versioning strategy (e.g., always on latest LTS, or specific patch versions for stability) to help maintain consistency.

[alexcos20]

AI automated code review (Gemini 3).

Overall risk: medium

Summary:
This pull request updates the Node.js version used in the Dockerfile from v20.19.0 to v22.15.0 and synchronizes the GitHub Actions CI workflows (ci.yml) to also utilize v22.15.0, including it in the test matrix.

Comments:
• [WARNING][other] The Node.js version in the Dockerfile is upgraded from v20.19.0 to v22.15.0. This is a jump across major LTS versions (assuming v22.x is LTS by the time of this commit, based on the future date).

While moving to a newer LTS is generally good for long-term support, security, and features, it's crucial to verify that all application dependencies and code are fully compatible with Node.js 22. Have comprehensive compatibility tests been performed, especially considering potential breaking changes between Node.js 20 and 22? Please provide any relevant migration guides or test results if available.
• [INFO][other] It's good to see that the CI configuration has been updated to consistently use v22.15.0 across various jobs and in the test matrix. This ensures that the application is built and tested against the new Node.js environment, aligning the development and deployment environments.
• [INFO][style] Using a specific patch version like v22.15.0 (instead of a floating tag like 22-alpine or 22) is good practice for reproducibility and stability in Docker builds.

[alexcos20]

AI automated code review (Gemini 3).

Overall risk: medium

Summary:
This pull request updates the Node.js version used in the Dockerfile from v20.19.0 to v22.15.0 and also updates all GitHub Actions CI workflows to use Node.js v22.15.0 (previously v22.5.1 or added to the test matrix for v22). This aims to align the development and testing environments with a newer Node.js LTS release.

Comments:
• [WARNING][other] The change from ENV NODE_VERSION=v20.19.0 to ENV NODE_VERSION=v22.15.0 is a major version upgrade. While Node.js 22 is an LTS release (as indicated by the branch name dockerfile-node-22), it's important to confirm that all project dependencies and application code are fully compatible with Node.js 22. Please ensure comprehensive regression tests are in place and passing to validate this upgrade.
• [INFO][other] It's good to see the CI workflows (audit, test, e2e-tests-unit, e2e-tests-integration, docker-test, test-coverage) updated to consistently use Node.js v22.15.0. This maintains consistency between the Docker image and the CI testing environment, which is crucial for reliable builds and deployments.
• [INFO][style] The test matrix now includes v22.15.0. Consider if 22.x or simply 22 (if Node.js 22 is already LTS and you want the latest patch) would be more appropriate here for easier maintenance, rather than pinning to a specific patch version like v22.15.0. Pinning to a specific patch version means you'll need to manually update this string for every future patch release, while 22.x or 22 would automatically pick up new patches.