[AriaEdo]

Summary

Upgrades Strapi from 5.59.0 to 5.61.0 (latest).

• @strapi/strapi, @strapi/plugin-cloud, @strapi/plugin-users-permissions: 5.59.0 → 5.61.0 (exact pins kept)
• @strapi/plugin-graphql: ^5.59.0 → ^5.61.0
• Lockfile regenerated; @strapi/core resolves to 5.61.0

Bumped manually via npm install because npx @strapi/upgrade crashes on Node 26 (MODULE_NOT_FOUND from esbuild-register). This is a minor release within v5, so no codemods apply.

Verification

• npm run build: admin panel builds
• npm run lint: 0 errors, 2 warnings (no source files changed)
• Smoke test with strapi start, run against both 5.59.0 and 5.61.0 on the same local DB. Every status code matched:
  • /_health 204, /admin 200
  • /api/articles, /api/authors, /api/categories 200
  • /api/global 404; /api/pages, /api/topics, /api/roadmaps, /api/twins-posts 403. These are identical on 5.59.0, most likely local public-role permissions and data.
  • GraphQL articles query returns {"data":{"articles":[]}}. The local DB has no articles, so this shows the endpoint responds but doesn't exercise real content.

Test plan

• Admin login and content editing in a preview/staging environment
• Verify REST/GraphQL responses against real content
• Review the 5.60/5.61 changelogs for behaviour changes

Notes

5.61.0 logs a new startup warning that the GraphQL maxLimit is unbounded. This is worth configuring in a follow-up.