[Bug]: Inconsistent database requirements

[fredericDelaporte]

Link to the documentation page or resource

https://docs.strapi.io/cms/deployment

Describe the bug

The Strapi cli installation page has different database version requirements than the deployment page.

Database	Recommended	Minimum
MySQL	8.4	8.0
MariaDB	11.4	10.3
PostgreSQL	17.0	14.0
SQLite	3	3

VS

Database	Recommended	Minimum
MySQL	8.0	8.0
MariaDB	10.6	10.5
PostgreSQL	14.0	12.0
SQLite	3	3

Additional context

It seems likely that is the deployment page which is outdated.

Suggested improvements or fixes

Determine what are the actual requirements and fix the pages needing fixing.

Related issue(s)/PR(s)

No response

[github-actions]

🤖 I've analyzed your question and here's what I found:

Thanks a lot for taking the time to report this and for providing clear tables and links — that’s really helpful for us.

You’re absolutely right: the CLI installation page and the deployment page currently list different database version requirements.

From the docs content:

• CLI installation page (current, higher versions): [CLI install]

  Database	Recommended	Minimum
  MySQL	8.4	8.0
  MariaDB	11.4	10.3
  PostgreSQL	17.0	14.0
  SQLite	3	3

• Deployment page (older, lower versions): [Deployment]

  Database	Recommended	Minimum
  MySQL	8.0	8.0
  MariaDB	10.6	10.5
  PostgreSQL	14.0	12.0
  SQLite	3	3

Given that the documentation is maintained to reflect the latest product guidance and that the CLI installation page is more recently aligned with other database docs (for example, the general database configuration page also lists MySQL 8.4 / 8.0, MariaDB 11.4 / 10.3, PostgreSQL 17.0 / 14.0, SQLite 3 / 3), the CLI installation table is the up‑to‑date one, and the deployment page is indeed outdated and should be updated. [Database config]

What this means for you right now

• You can safely rely on the CLI installation page (and the database configuration page) for the correct, current database version requirements.
• The deployment page will need to be brought in line with those values.

Next steps on our side

• We’ll flag this inconsistency so the docs team can:
  • Update the deployment page’s database table to match the CLI installation and database configuration pages.
  • Ensure we have a single source of truth for supported database versions to avoid this kind of drift in the future.

Thanks again for catching this and for suggesting exactly what needed to be done (determine the actual requirements and fix the pages). Contributions like yours really help keep the docs accurate for everyone.

If you’d like to follow along or propose wording changes, you’re also very welcome to open or link a PR in the strapi/documentation repo, but it’s absolutely not required — we’ll take it from here. You can also reach out on the forum or Discord if you have any follow‑up questions.

📚 Relevant documentation:

• Community & Support
• Database configuration
• Database configuration - Configuration examples
• Database configuration - Database management by environment
• Database configuration - Databases installation
• Database configuration - Environment variables in database configurations
• Deployment
• Installing from CLI
• Installing from CLI - CLI installation options
• MySQL v5 is not supported in Strapi v5 anymore
• Only the mysql2 package is supported for the MySQL client
• Release notes - 5.6.3
• Release notes - 6.6.6
• Why SQLite should not be used in production

---

ℹ️ This response was generated automatically. If this doesn't fully answer your question or if you need further assistance, please mention @pwizla in a comment and a human maintainer will help you.

You can also try our interactive AI chat for more detailed assistance.

💡 For feature requests or product feedback, visit feedback.strapi.io.