chore: forward-port release-1.2

Signed-off-by: Francesco Noacco <francesco.noacco@secomind.com>

Author: noaccOS

CHANGELOG.md

@@ -104,15 +104,18 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 - [astarte_data_updater_plant] Correctly encode values when sending properties to device on connection
 - [astarte_realm_management] Allow to delete long-disconnected devices. For this to work, Realm Management needs `CLUSTERING_STRATEGY`, `CLUSTERING_KUBERNETES_NAMESPACE` and `DATA_UPDATER_PLANT_CLUSTERING_KUBERNETES_SELECTOR` to be set, just like AppEngine and DUP. Refer to 1.2.1-rc.0 for additional information on the variables.
 
-## [1.2.1] - Unreleased
+## [1.2.1] - 2026-03-12
 
 ### Fixed
 
 - [astarte_realm_management] Insufficient validation for conflicting options in interface aggregate mappings
   [#1072](https://github.com/astarte-platform/astarte/issues/1072)
+- [astarte_data_updater_plant] Ensure device deletion rpc always checks updated status
 
 ## [1.2.1-rc.1] - 2026-02-13
 
+### Fixed
+
 - [astarte_realm_management] Bug where devices got stuck in the "in deletion" status: [#1493](https://github.com/astarte-platform/astarte/issues/1493).
 - [astarte_data_updater_plant] Correctly reconnect to AMQP after a connection loss
 - [astarte_data_updater_plant] Fix possible crash when sending data on interface-specific volatile triggers

README.md

@@ -1,7 +1,7 @@
 # Astarte
 
-![](https://github.com/astarte-platform/astarte/workflows/Build%20and%20Test%20Astarte%20Apps/badge.svg?branch=v1.2.0)
-[![codecov](https://codecov.io/gh/astarte-platform/astarte/tag/v1.2.0/graph/badge.svg)](https://codecov.io/gh/astarte-platform/astarte)
+![](https://github.com/astarte-platform/astarte/workflows/Build%20and%20Test%20Astarte%20Apps/badge.svg?branch=v1.2.1)
+[![codecov](https://codecov.io/gh/astarte-platform/astarte/tag/v1.2.1/graph/badge.svg)](https://codecov.io/gh/astarte-platform/astarte)
 
 <img src="doc/images/mascotte.svg" align="left" width="160px" />Astarte is an Open Source IoT
 platform focused on Data management and processing written in [Elixir](https://github.com/elixir-lang/elixir).
@@ -34,7 +34,7 @@ Can't be easier. Pick your favorite machine with at least 4GB of free RAM, make
 [Docker](https://www.docker.com/), and simply:
 
 ```sh
-$ git clone https://github.com/astarte-platform/astarte.git -b v1.2.0 && cd astarte
+$ git clone https://github.com/astarte-platform/astarte.git -b v1.2.1 && cd astarte
 $ docker run -v $(pwd)/compose:/compose astarte/docker-compose-initializer:1.1
 $ docker compose pull
 $ docker compose up -d

apps/astarte_data_updater_plant/lib/astarte_data_updater_plant/data_updater/impl.ex

@@ -117,6 +117,9 @@ defmodule Astarte.DataUpdaterPlant.DataUpdater.Impl do
   end
 
   def start_device_deletion(state, timestamp) do
+    # Force deletion status check
+    state = %{state | last_deletion_in_progress_refresh: 0}
+
     # Device deletion is among time-based actions
     new_state = TimeBasedActions.execute_time_based_actions(state, timestamp)
 

apps/astarte_data_updater_plant/lib/astarte_data_updater_plant/data_updater/server.ex

@@ -20,7 +20,7 @@ defmodule Astarte.DataUpdaterPlant.DataUpdater.Server do
   @moduledoc """
   This module implements the GenServer responsible for managing the state of a single device in the DataUpdaterPlant.
   """
-  use GenServer
+  use GenServer, restart: :transient
   alias Astarte.DataUpdaterPlant.Config
   alias Astarte.DataUpdaterPlant.DataUpdater.Core
   alias Astarte.DataUpdaterPlant.DataUpdater.Impl

apps/astarte_data_updater_plant/lib/astarte_data_updater_plant/message_tracker/server.ex

@@ -21,7 +21,7 @@ defmodule Astarte.DataUpdaterPlant.MessageTracker.Server do
   This module implements the GenServer responsible for tracking the messages.
   """
   require Logger
-  use GenServer
+  use GenServer, restart: :transient
 
   @base_backoff 1000
   @random_backoff 9000

doc/pages/architecture/030-interface.md

@@ -152,7 +152,7 @@ The following types are supported:
 - `doublearray`, `integerarray`, `booleanarray`, `longintegerarray`, `stringarray`,
   `binaryblobarray`, `datetimearray`: A list of values, represented as a JSON Array. Arrays can have
   up to 1024 items and each item must respect the limits of its scalar type (_i.e._ each string in a
-  `stringarray` must be at most 65535 bytes long, each binary blob in a `binaryblobarray` must be
+  `stringarray` must be at most 65536 bytes long, each binary blob in a `binaryblobarray` must be
   shorter than 64 KiB.
 
 Make sure that the differences between two distinct interface names are not limited to the casing or

doc/pages/tutorials/010-astarte_in_5_minutes.md

@@ -60,8 +60,8 @@ Ubuntu 22.04 and macOS 10.15 Catalina, but any other modern operating system sho
 To get our Astarte instance running as fast as possible, we will install Astarte's standalone distribution. It includes a tunable Docker Compose which brings up Astarte and every companion service needed for it to work. To do so, simply clone Astarte's main repository and use its scripts to bring it up:
 
 ```sh
-$ git clone https://github.com/astarte-platform/astarte.git -b v1.2.0 && cd astarte
-$ docker run -v $(pwd)/compose:/compose astarte/docker-compose-initializer:1.2.0
+$ git clone https://github.com/astarte-platform/astarte.git -b v1.2.1 && cd astarte
+$ docker run -v $(pwd)/compose:/compose astarte/docker-compose-initializer:1.2.1
 $ docker compose pull
 $ docker compose up -d
 ```

doc/pages/user/040-connect_device.md

@@ -21,12 +21,12 @@ Secret_. This _Credentials Secret_ is the token the device uses for performing t
 routine, which results in the device obtaining its Credentials for accessing its designated
 Transport.
 
-A Device's _Credentials Secret_ allows access to [Pairing API's Device REST API](https://docs.astarte-platform.org/astarte/1.1/api/?urls.primaryName=Pairing%20API#/device),
+A Device's _Credentials Secret_ allows access to [Pairing API's Device REST API](https://docs.astarte-platform.org/astarte/1.2/api/?urls.primaryName=Pairing%20API#/device),
 which is then used for obtaining information about which Transports the Device can use for
 communicating, and for obtaining Credentials for its assigned Transports.
 
-The ability to request Credentials of a Device can be inhibited with [AppEngine API](https://docs.astarte-platform.org/astarte/1.1/api/#/device/updateDeviceStatus) or using
-[`astartectl`](https://github.com/astarte-platform/astartectl) with this command:
+The ability to request Credentials of a Device can be inhibited with [AppEngine API](https://docs.astarte-platform.org/astarte/1.2/api/#/device/updateDeviceStatus)
+or using [`astartectl`](https://github.com/astarte-platform/astartectl) with this command:
 
 ```bash
 astartectl appengine devices credentials inhibit <device_id_or_alias> true \

doc/pages/user/080-grafana_datasource.md

@@ -14,7 +14,7 @@ You can browse the source code of this plugin on its
 ## Try it!
 
 When deploying locally using `docker-compose` as mentioned in the
-[Astarte in 5 mins tutorial](https://docs.astarte-platform.org/astarte/1.1/010-astarte_in_5_minutes.html#install-astarte),
+[Astarte in 5 mins tutorial](https://docs.astarte-platform.org/astarte/1.2/010-astarte_in_5_minutes.html#install-astarte),
 Astarte Datasource Plugin will be automatically installed. You may then access Grafana
 by visiting http://grafana.astarte.localhost.
 

docker-compose.yml

@@ -143,7 +143,7 @@ services:
       - "scylla"
 
   astarte-dashboard:
-    image: astarte/astarte-dashboard:1.2-snapshot
+    image: astarte/astarte-dashboard:snapshot
     volumes:
       - ./compose/astarte-dashboard/config.json:/usr/share/nginx/html/user-config/config.json:z
     depends_on:
@@ -255,7 +255,7 @@ services:
 
   # VerneMQ
   vernemq:
-    image: astarte/vernemq:1.3.0-rc.1
+    image: astarte/vernemq:1.3-snapshot
     hostname: vernemq
     env_file:
       - ./.env