diff --git a/source/_integrations/mqtt.markdown b/source/_integrations/mqtt.markdown
index 2282cd1a0a0..661b9af808a 100644
--- a/source/_integrations/mqtt.markdown
+++ b/source/_integrations/mqtt.markdown
@@ -1475,10 +1475,6 @@ The MQTT integration will register the `mqtt.publish` action, which allows publi
 When `payload` is rendered from [template](/docs/configuration/templating/#using-templates-with-the-mqtt-integration) in a YAML script or automation, and the template renders to a `bytes` literal, the outgoing MQTT payload will only be sent as `raw` data, if the `evaluate_payload` option flag is set to `true`.
 {% endnote %}
 
-{% important %}
-You must include either `topic` or `topic_template`, but not both. If providing a payload, you need to include either `payload` or `payload_template`, but not both.
-{% endimportant %}
-
 ```yaml
 topic: homeassistant/light/1/command
 payload: on
diff --git a/source/_posts/2025-02-05-release-20252.markdown b/source/_posts/2025-02-05-release-20252.markdown
index a450b0b2902..22e26ac17c3 100644
--- a/source/_posts/2025-02-05-release-20252.markdown
+++ b/source/_posts/2025-02-05-release-20252.markdown
@@ -815,8 +815,14 @@ entry context menu.
 
 ([@jbouwh] - [#133342]) ([documentation](/integrations/mqtt))
 
+
+The MQTT publish action no longer supports the `topic_template` and `payload_template` attributes. Instead, only `topic` and `payload` should be used. In automation and scripts, users can use templates by default. Users were instructed to update their automations and scripts with a repair flow when the use of the deprecated action options was detected.
+
+([@jbouwh] - [#134056]) ([documentation](/integrations/mqtt))
+
 [@jbouwh]: https://github.com/jbouwh
 [#133342]: https://github.com/home-assistant/core/pull/133342
+[#134056]: https://github.com/home-assistant/core/pull/134056
 
 {% enddetails %}