chore(deps): upgrade Strapi to 5.53.0

[AriaEdo]

Summary

• Bump @strapi/strapi, @strapi/plugin-cloud, @strapi/plugin-graphql, and @strapi/plugin-users-permissions from 5.34.0 to 5.53.0 (latest).
• Remove the global zod override, which forced zod v4 onto every nested dependency and broke koa-session (a new transitive dependency of @strapi/core 5.53 that requires zod v3's API). Without the override, npm resolves per-package zod versions naturally — our own code still gets zod v4, koa-session gets its own zod v3.
• Bump engines.node minimum to >=20.0.0 to match Strapi 5.53's requirement.
• Regenerate types/generated/*.d.ts for the new admin schema (api-token/permission relations, upload focal point, session metadata).

Test plan

• npm install completes cleanly
• npm run build succeeds
• npm run develop boots the server successfully on Strapi 5.53.0
• Manual smoke test in a deployed/staging environment (admin login, content editing, uploads)

🤖 Generated with Claude Code

[Copilot]

🟡 Changes recommended

Update the lockfile metadata and documentation to match the dependency and Node.js version changes.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Upgrades Strapi and related plugins to 5.53.0, removes the global Zod override, raises the Node.js minimum to 20, and refreshes generated typings.

Changes:

• Updated Strapi dependencies and Zod resolution.
• Updated the Node.js engine requirement.
• Regenerated content-type and component declarations.

File summaries

File	Summary
types/generated/contentTypes.d.ts	Regenerated Strapi schema typings.
types/generated/components.d.ts	Updated generated component declarations.
package.json	Updated dependencies, Zod handling, and Node.js requirements.

Review details

Suppressed comments (1)

package.json:26

• This dependency bump leaves PROJECT_ANALYSIS.md inconsistent with the repository: it still documents Strapi and the three plugins at 5.34.0 (and Node >=18). Please update that version table with this upgrade so the project's deployment/development requirements are not misreported.

    "@strapi/plugin-cloud": "5.53.0",
    "@strapi/plugin-graphql": "^5.53.0",
    "@strapi/plugin-users-permissions": "5.53.0",
    "@strapi/strapi": "5.53.0",

• Files reviewed: 1/4 changed files
• Comments generated: 2
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ AriaEdo
❌ Copilot
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[Copilot]

🟡 Changes recommended

Update the lockfile metadata and documentation to match the dependency and Node.js version changes....

Addressed the linked review feedback in commits ee2fc15 and f3736e0 (lockfile metadata and documentation alignment).

[Copilot]

🔵 Needs a closer look

Resolve the Apollo Server EOL dependency and align the Node.js engine and documentation ranges with the resolved dependencies.

Review details

Suppressed comments (3)

docs/LOCAL_DEVELOPMENT.md:7

• This prerequisite now says Node 20–22, but the changed package.json engine declares Node 20–24 as supported. That makes the local-development guide incorrectly exclude Node 23 and 24; either document the full supported range or narrow the engine declaration to match the actual support policy.

- **Node.js**: 20.x–24.x

package.json:24

• The upgraded GraphQL plugin still pins @apollo/server to 4.13.0 (package-lock.json:6197), and npm marks Apollo Server v4 as end-of-life since January 26, 2026. Since config/plugins.js:5-8 enables the /graphql endpoint, this keeps an EOL server in the deployed runtime; please use a compatible Strapi/plugin release that supports Apollo Server 5 or explicitly resolve the compatibility/update plan before merging.

    "@strapi/plugin-graphql": "^5.53.0",

package.json:40

• The new lower bound is too low for the resolved dependency tree: @strapi/upload now installs sharp@0.35.3, whose lockfile entry requires Node >=20.9.0. This advertises Node 20.0–20.8 as supported even though npm will report an engine mismatch and upload/image processing is unsupported there. Raise the project minimum to >=20.9.0 and update the local-development prerequisite, or retain 20.0 support only by selecting compatible dependency versions.

    "node": ">=20.0.0 <=24.x.x",

• Files reviewed: 3/6 changed files
• Comments generated: 0 new
• Review effort level: Lite

[Copilot]

🔵 Needs a closer look

The dependency and runtime changes warrant final human review.

Review details

• Files reviewed: 3/6 changed files
• Comments generated: 0 new
• Review effort level: Lite