:_mod-docs-content-type: REFERENCE
[id="multi-arch-tuning-operator-release-notes-1-2-0_{context}"]
= Release notes for the Multiarch Tuning Operator 1.2.0

[role="_abstract"]
The release notes for the Multiarch Tuning Operator 1.2.0 summarize all new features and enhancements, notable technical changes, major corrections from the previous version, and any known bugs upon general availability.

Issued: 22 October 2025

[id="multi-arch-tuning-operator-1-2-0-new-features-and-enhancements_{context}"]
== New features and enhancements

* With this release, you can enable the `exec format error monitor` plugin for the Multiarch Tuning Operator. This plugin detects `ENOEXEC` errors, which occur when a pod attempts to execute a binary incompatible with the node's architecture. You enable this plugin by setting the `plugins.execFormatErrorMonitor.enabled` parameter to `true` in the `ClusterPodPlacementConfig` object. For more information, see xref:../../post_installation_configuration/configuring-multi-arch-compute-machines/multiarch-tuning-operator.adoc#multi-architecture-creating-podplacement-config_multiarch-tuning-operator[Creating the ClusterPodPlacementConfig object].

[id="multi-arch-tuning-operator-1-2-0-bug-fixes_{context}"]
== Bug fixes

* Previously, the Multiarch Tuning Operator incorrectly handled the Operator bundle image inspector, restricting the inspector to a single architecture, which could cause OLM to fail when installing Operators. With this update, MTO now sets the bundle image to support all architectures, allowing Operators to be successfully installed on single-architecture clusters when the Multiarch Tuning Operator is deployed. (link:https://issues.redhat.com/browse/MULTIARCH-5546[MULTIARCH-5546])

* Previously, when a cluster global pull secret was changed, stale authentication information could remain in the Multiarch Tuning Operator cache. With this update, the cache is cleared whenever a cluster global pull secret is changed. (link:https://issues.redhat.com/browse/MULTIARCH-5538[MULTIARCH-5538])

* Previously, the Multiarch Tuning Operator failed to process pods if an image reference contained both a tag and a digest. With this update, the image inspector prioritizes the digest if both are present. (link:https://issues.redhat.com/browse/MULTIARCH-5584[MULTIARCH-5584])

* Previously, the Multiarch Tuning Operator did not respect the `.spec.registrySources.containerRuntimeSearchRegistries` field in the `config.openshift.io/Image` custom resource when a workload image did not specify a registry URL. With this update, the Operator can now handle this case, allowing workload images without an explicit registry URL to be pulled successfully. (link:https://issues.redhat.com/browse/MULTIARCH-5611[MULTIARCH-5611])

* Previously, if the `ClusterPodPlacementConfig` object was deleted less than 1 second after its creation, some finalizers were not removed in time, causing certain resources to remain. With this update, all finalizers are properly deleted when the `ClusterPodPlacementConfig` object is deleted. (link:https://issues.redhat.com/browse/MULTIARCH-5372[MULTIARCH-5372])
