01 · LIFECYCLE

Magento versions, end-of-support dates &
system requirements
in one place.

A tracker for engineers, DevOps and BAs running Magento Open Source, Adobe Commerce or Mage-OS. Release dates, security windows, and system requirements — readable by humans and agents alike.

Browse releases Read the API docs

232: versions tracked
3: distributions
9: JSON endpoints
0: auth required

Lifecycle horizon

End of support across distributions

2026

2027

2028

2029

2.4.7-p10 OSS / Commerce

Apr 9, 2027

2.4.8-p5 OSS / Commerce

Apr 11, 2028

2.4.9 OSS / Commerce

May 12, 2029

Today — Oct 8, 2026 Ends in < 12 months Supported

02 · QUICK ANSWER

The current Magento version, at a glance

The current Magento Open Source version is 2.4.9, released May 12, 2026, with end of support on May 12, 2029. The current Adobe Commerce version is 2.4.9.

PHP: 8.5
MySQL / MariaDB: 8.4
OpenSearch / Elasticsearch: 3
Status: supported (latest)

03 · DISTRIBUTIONS

Three distributions, one lifecycle tracker

magento-community

Magento Open Source

The free, community-maintained edition of Magento 2.

Latest: 2.4.9
Tracked: 111 versions
Status: active

Browse releases →

magento-commerce

Adobe Commerce

Adobe's commercial distribution, tracked alongside Open Source.

Latest: 2.4.9
Tracked: 111 versions
Status: active

Browse releases →

mage-os

Mage-OS

Community-driven fork of Magento Open Source, released on its own cadence.

Latest: 3.5.0
Tracked: 10 versions
Status: active

Browse releases →

04 · API

JSON over HTTP. No auth. No rate limits worth worrying about.

Replace {distribution} with magento-community, magento-commerce, or mage-os.

GET /api/v1/{distribution}/versions All versions with full lifecycle data
GET /api/v1/{distribution}/versions/supported Currently supported versions
GET /api/v1/{distribution}/versions/secure Versions receiving security updates
GET /api/v1/{distribution}/versions/latest Latest stable release
GET /api/v1/{distribution}/versions/{version} Specific version (e.g., 2.4.7)
GET /api/v1/{distribution}/versions/{version}/security Which bulletins affect this version, and the fix
GET /api/v1/security-bulletins All Adobe/Magento security bulletins
GET /api/v1/security-bulletins/{id} One security bulletin by id
GET /api/v1/health Health check

Read the full API documentation →

05 · MCP SERVER

Ask your coding agent about Magento versions.

Drop the magento.watch MCP server into Claude, Cursor, or any MCP-aware client. Your agent can look up release dates, end-of-support windows, and system requirements through the same endpoints this page uses.

Installation →

~/.config/claude/mcp.json

{
  "mcpServers": {
    "magento-watch": {
      "url": "https://magento.watch/mcp/api",
      "transport": "http"
    }
  }
}

06 · SYSTEM REQUIREMENTS

The stack, per version.

PHP

8.2, 8.3

Composer

2.10

MariaDB

10.11, 11.8

Elasticsearch

OpenSearch

2.19, 3

RabbitMQ

4.3

Valkey

8.1

Varnish

Nginx

1.30

ActiveMQ

AWS Aurora MySQL

8.0

AWS S3

supported

AWS MQ

3.13

AWS ElastiCache

redis-7.1

AWS OpenSearch

3.1

PHP

8.3, 8.4

Composer

2.10

MySQL

8.4

MariaDB

11.4, 11.8

Elasticsearch

OpenSearch

RabbitMQ

4.3

Valkey

8.1

Varnish

Nginx

1.30

ActiveMQ

AWS Aurora MySQL

8.0

AWS S3

supported

AWS MQ

3.13

AWS ElastiCache

redis-7.1

AWS OpenSearch

3.1

PHP

8.5

Composer

2.10

MySQL

8.4

MariaDB

11.8, 12.3

OpenSearch

RabbitMQ

4.3

Valkey

Varnish

Nginx

1.30

ActiveMQ

AWS Aurora MySQL

8.0

AWS S3

supported

AWS MQ

3.13

AWS ElastiCache

redis-7.1

AWS OpenSearch

3.1

PHP

8.3, 8.4

Composer

2.9

MySQL

8.4

MariaDB

11.4

OpenSearch

RabbitMQ

4.1

Valkey

Varnish

7.7

Nginx

1.28

ActiveMQ

AWS Aurora MySQL

8.0

AWS S3

supported

AWS MQ

3.13

AWS ElastiCache

redis-7

AWS OpenSearch

2.5

Fields shown reflect only the keys present on this version. Sparse by design — absence means “not declared,” not “incompatible.”

07 · FAQ

Answers in one scroll.

01 What is the current latest Magento version? –

magento.watch tracks the latest Magento Open Source, Adobe Commerce and Mage-OS releases live. The number shown in the hero and in the JSON API is recomputed on every request from the canonical data file.

See current version →JSON API →

02 When does Magento 2.4.x reach end of support? +

Every Magento 2.4.x version gets three years of full support from its general-availability date. See the /versions page for the exact end-of-support date of every tracked release.

End-of-support list →Supported list →

03 What does the API return for each version? +

Only the fields we actually track: version, releaseDate, eolDate, and systemRequirements. At request time the API also derives boolean flags (isFutureVersion, isEOLVersion, isSecureVersion, isLatestVersion) and a statusLabel. List responses add a securitySummary with the Adobe security patches each release still needs; single-version responses carry the full security report. No changelogs, download URLs, or migration guides.

API reference →MCP server →

04 Is the API free to use? +

Yes. Public, read-only, no auth. Please cache responses if you intend to poll — the service is self-funded.

Browse versions →

05 How is a version’s status determined? +

statusLabel is one of: upcoming (future releaseDate), supported (latest), supported, eol (past eolDate), or unknown (releaseDate or eolDate missing). isSecureVersion is simply: released and not past end of support. It describes the lifecycle, not the patch level: a supported release can still need isolated security patches, which securitySummary lists as requiredPatches.

Status vocabulary →Per-version pages →

06 Why is Mage-OS empty? +

The distribution is registered so the endpoint shape stays consistent, but no versions are indexed yet. /api/v1/mage-os/versions returns an empty set until we have data.

Mage-OS releases →

07 Why can systemRequirements look different between versions? +

The schema is sparse. A version may declare MySQL but not MariaDB, or Redis but not Valkey. Absent keys mean “not declared,” not “incompatible.” AWS-managed equivalents may report "supported" instead of a version string.

Browse versions →Latest release →

08 How should I sort version strings? +

Don’t sort them lexically — 2.4.8-p10 would land before 2.4.8-p9. Treat version as an opaque key and order by releaseDate instead.

API field reference →

The current Magento version, at a glance

Three distributions, one lifecycle tracker

Magento Open Source

Adobe Commerce

Mage-OS

JSON over HTTP. No auth. No rate limits worth worrying about.

Ask your coding agent about Magento versions.

The stack, per version.

Answers in one scroll.

Łukasz Bajsarowicz, e-commerce architect