Mappia Service Versioning Policy

Mappia couples Magento application versioning with its supporting service dependency stack. This policy governs how Mappia determines, defaults, and overrides service versions such as MariaDB, Opensearch, Redis, RabbitMQ.

How versions are determined

When Adobe releases a new version of Magento, we review the updated System Requirements and update the tags@magento.latest value accordingly. This includes upgrading dependency versions to match the new Magento release. The same process applies to any newly introduced tags.

Post End-of-life Magento Patch Versions

For end-of-life patch versions of Magento where a newer patch in the same release line exists (e.g., Magento 2.4.7-p3 when 2.4.7-p4 is available), Mappia defaults to the latest minor or patch version of each dependency within the same major version. This may result in using a version not explicitly listed in Adobe's documentation if that version remains within the officially supported major version range.

Example: Magento 2.4.7-p3 lists opensearch:2.12 as the supported version. However, OpenSearch follows a rolling maintenance model within major versions. As such, Mappia deploys opensearch:2.19.1 (latest at time of writing) for the tag tags.magento@2.4.7-p3.

TIP

If you encounter errors using an older version of Magento on a newer dependency version, please create a post about it and we can provide guidance on whether or not this is fixable.

This policy also applies to:

• Redis
• OpenSearch
• RabbitMQ
• MariaDB

Default Behavior

Mappia ships with system requirements versions as tags under tags.magento@$version. These tags map Magento versions (including patch versions) to supported versions of critical services. If a given tag is set to true, the chart will use these values automatically.

By default the tag tags@magento@latest is enabled, rolling out the most recent version of infrastructure for Magento 2.

DANGER

These tags are intended to be used exclusively (enabling one means that you disable another), you should not combine tags. Any such resulting behavior is undocumented. Here lie dragons.

Major Service Version Upgrades

In certain cases, major version upgrades of service dependencies require deploying a second chart alongside the existing version. This is necessary for stateful services such as OpenSearch, MariaDB, and RabbitMQ, where in-place upgrades risk data loss or corruption.

When such a split deployment is required, it will be documented in the changelog and upgrade guide, including any required migration steps. These steps must be followed to avoid data loss.

Overriding

If your application depends on a specific version of a dependency, or you encounter incompatibilities with your Magento store due to this policy, you can override the default by specifying a different image or tag for the affected service. We also strongly encourage to you post about this so that we can document and potentially fix it.

These overrides allow you to downgrade or upgrade as needed:

sessioncache:
  image:
    tag: "6.2.7"