Bump node version

[snowmous3]

Description

Good news! You're already running Node.js v20.11.0 locally, so the project should work immediately. The dependencies in your package.json (TypeScript 4.3.5, Next.js 12.1.0, NestJS 9.2.0, etc.) are all compatible with Node.js v20

1. .node-version - Updated from 18.19.1 to 20.18.0
2. Dockerfile - Updated both base images:
   • Line 1: FROM node:20.18.0-alpine AS package
   • Line 65: FROM node:20.18.0-alpine
3. .github/workflows/nodejs.yml - Updated all Node version matrix entries:
   • test-docker job: 20.18.0
   • build job: 20.18.0
   • test-lint job: 20.18.0
4. .github/workflows/docs.yml - Updated Node version to 20.18.0 (also fixed missing matrix definition)
5. package.json - Added engines field to specify minimum Node version:
   "engines": {
   "node": ">=20.18.0"
   }

Related Ticket # (issue)

Type of change

• Existing feature enhancement (non-breaking change which modifies existing functionality)

Testing

1. Test the build locally: yarn build
2. Run tests to ensure everything works: yarn test
3. Commit these changes when ready

Developer Checklist

General

• Code is appropriately commented, particularly in hard-to-understand areas
• Repository documentation has been updated (Readme.md) with additional steps required for a local environment setup.
• No console.log or related logging is added.
• No code is repeated/duplicated in violation of DRY. The exception to this is for new (MVP/Prototype) functionality where the abstraction layer may not be clear (comments should be added to explain the violation of DRY in these scenarios).
• Documented with TSDoc all library and controller new functions

Frontend Changes

• No new styling is added through CSS files (Unless it's a bugfix/hotfix)
• All types are added correctly

Backend Changes

• All endpoints are appropriately secured with Middleware authentication
• All new endpoints have a interface schema defined

Tests

• All existing unit and end to end tests pass across all services
• Unit and end to end tests have been added to ensure backend APIs behave as expected

Test IDs

• Include the test ID when adding new tasks or components.
• Check that test IDs are present in the modified components.

Merge Request Review Checklist

• An issue is linked to this PR and these changes meet the requirements outlined in the linked issue(s)
• High risk and core workflows have been tested and verified in a local environment.
• Enhancements or opportunities to improve performance, stability, security or code readability have been noted and documented in Project do Github issues if not being addressed.
• Any dependent changes have been merged and published in downstream modules
• Changes to multiple services can be deployed in parallel and independently. If not, changes should be broken out into separate merge requests and deployed in order.

[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

[caneppelevitor]

Hey @snowmous3 what are the plans to test this bump, we will merge it on the stage environment or do you have other approach in mind ?

[snowmous3]

Hey @snowmous3 what are the plans to test this bump, we will merge it on the stage environment or do you have other approach in mind ?

I'm thinking of merging first to stage, waiting some days until moving it to prod/release

[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