> ## Documentation Index
> Fetch the complete documentation index at: https://astronomer.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Remote Execution Agent release notes

<Tip>[Subscribe to Remote Execution Agent release notes](/docs/astro/release-notes-subscribe) to receive updates via RSS, email, or Slack.</Tip>

<Note> This is feature is only available if you are on the **Enterprise** tier or above. See [Astro Plans and Pricing](https://www.astronomer.io/pricing/).</Note>

<Info>
  **Remote Execution Agent image release cadence**

  New Remote Execution Agent images are typically released when an Astro Runtime based on a new Airflow version becomes available, or when critical bug or security fixes are required for an existing Runtime or Airflow version.

  You can expect the updated Agent image to be published within **seven days** of the corresponding Runtime image release.
</Info>

<Warning>
  **Helm chart now versioned independently from the Remote Execution Agent**

  As of May 2026, the Remote Execution Agent Helm chart is versioned separately from the Agent, so chart releases no longer appear on this page. Helm chart 2.0.0 introduces a breaking change for upgrades from 1.x that requires action before you run `helm upgrade`. See [Helm chart versioning](/docs/astro/agent-maintenance-policy#helm-chart-versioning) for the compatibility matrix and upgrade steps.
</Warning>

The Astro Remote Execution Agent allows you to run your Airflow tasks remotely in your Kubernetes cluster, connecting to an existing Astro Deployment. This Agent provides the following components:

* Workers: Execute tasks from specified queues.
* Dag processor: Process and sync Dags from configured sources.
* Triggerer: Handle deferrable operators and triggers.

To upgrade Remote Execution Agent, see [Upgrade Remote Execution Agent](/docs/astro/agent-maintenance-policy). For general product release notes, see [Astro Release Notes](/docs/astro/release-notes). If you have any questions or a bug to report, contact [Astronomer support](https://cloud.astronomer.io/open-support-request).

## Known issues

The following known issues apply to all current Remote Execution Agent releases:

* The Dag processor supports reading Airflow variables, but you cannot currently create, update, or delete variables from the Dag processor.

<Update label="Astro Remote Execution Agent and Sentinel 1.8.3" description="July 23, 2026">
  #### Additional improvements

  * Updated bundled dependencies to address security vulnerabilities in `click`.

  #### Images included

  See [Astro Remote Execution Agent 1.8.3 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-8-3).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.8.2" description="July 17, 2026">
  #### Additional improvements

  * Improved how the worker, Dag processor, and triggerer components communicate with the Astro control plane to better support future Airflow versions.

  #### Bug fixes

  * Fixed a bug that could cause an agent component to send an unnecessary internal header on requests to the Astro control plane.

  #### Images included

  See [Astro Remote Execution Agent 1.8.2 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-8-2).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.8.1" description="July 15, 2026">
  #### Additional improvements

  * [Task-level utilization metrics](/docs/astro/task-level-metrics) support extends to all supported Remote Execution Agent versions 1.5.0 and later using the Helm 2.0.0+ chart.

  #### Bug fixes

  * Fixed a bug introduced in 1.8.0 where Remote Execution Agents on Astro Runtime versions earlier than 3.3, such as Runtime 3.2, failed to start because the agent incorrectly required a worker-side state store backend that those runtimes don't include. The agent now requires the backend only on Astro Runtime 3.3 and later images.
  * Fixed a bug where the local HTTP proxy in the agent could stop forwarding task heartbeats when an unresponsive upstream connection held a connection-pool slot indefinitely. The proxy client now sets explicit timeouts.

  #### Images included

  See [Astro Remote Execution Agent 1.8.1 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-8-1).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.8.0" description="July 15, 2026">
  #### Airflow 3.3 support

  Agent Client now supports Airflow 3.3 ([Astro Runtime 3.3-2](/docs/runtime/runtime-release-notes#astro-runtime-3-3-2)), with images for Python 3.12, 3.13, and 3.14. This includes support for the Airflow 3.3 worker-side state store: agents offload task and asset state to a backend that you configure, such as object storage, instead of storing it in the Astro control plane. Asset-watcher triggers running in the agent triggerer can also access the asset state store.

  When you run agents on a Runtime 3.3 image, you must [configure a state store backend](/docs/astro/remote-execution-configure-state-store-backend) through the `AIRFLOW__WORKERS__STATE_STORE_BACKEND` environment variable. Agents on Runtime 3.3 images do not start until you set this variable.

  #### Additional improvements

  * The Dag processor now caches parsed Dags by default and sends only new and changed Dags on each heartbeat, instead of every serialized Dag. Set `ASTRO_AGENT_CLIENT_DAG_PROCESSOR__ENABLE_DAG_CACHING=false` to opt out.
  * Agents now detect DNS changes for the Astro control plane and re-create their connections, so they reconnect automatically after a disaster recovery failover instead of requiring a restart.
  * New Agent Client releases no longer publish floating image tags, such as `3.2-5` or `3.2-5-python-3.13`. Existing floating tags remain in the registry but no longer receive updates. Use the pinned tags listed in the [Remote Execution Agent image reference](/docs/astro/agent-images), as recommended by the [Agent maintenance policy](/docs/astro/agent-maintenance-policy#image-tag-naming-conventions).
  * Where Sentinel is integrated, agent components now report an initializing status while their Pods start up, instead of briefly reporting as unhealthy.
  * Reduced Sentinel memory usage by excluding Kubernetes managed fields from the Pod cache.
  * The control plane now manages the Sentinel heartbeat interval, as it already does for the heartbeat intervals of other agent components.
  * Updated bundled dependencies to address security vulnerabilities in `cryptography`, `pyjwt`, `python-multipart`, and `starlette`.

  #### Bug fixes

  * Fixed a bug where the Dag processor on Airflow versions earlier than 3.3 did not respect configured Dag bundle refresh intervals, so bundles could refresh too often or on another bundle's schedule.
  * Fixed a bug where unpausing a Dag that uses asset watchers did not create the watcher triggers with Dag caching enabled. Dags that use asset watchers are now excluded from Dag caching.
  * Fixed a bug where Dag-level and task-level callbacks that pull XComs failed with `ForbiddenSessionUseError`, which could repeatedly crash the Dag processor on Airflow 3.1. The Dag processor now serves callback XCom reads through the Astro control plane.
  * Fixed a bug where a task that completed within a single metrics-collection interval produced a metrics record that the control plane rejected, blocking the whole metrics batch and causing repeated `Failed to send task metrics` errors.
  * Fixed docstring redaction for task groups: the Dag processor now redacts `doc_md` in addition to `tooltip`, including on task groups nested more than one level deep, before Dags leave the agent.
  * Fixed a bug where the Dag processor could send stale parse results to the control plane after a Dag bundle version update.

  #### Images included

  See [Astro Remote Execution Agent 1.8.0 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-8-0).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.7.4" description="July 23, 2026">
  #### Additional improvements

  * Updated Agent Client images to include the [3.2-6 Runtime version](/docs/runtime/runtime-release-notes#astro-runtime-3-2-6).
  * Updated bundled dependencies to address security vulnerabilities in `click`.

  #### Images included

  See [Astro Remote Execution Agent 1.7.4 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-7-4).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.7.3" description="July 14, 2026">
  #### Additional improvements

  * Updated bundled dependencies to address security vulnerabilities in `cryptography`, `pyjwt`, `python-multipart`, and `starlette`.

  #### Bug fixes

  * Fixed a bug where the local HTTP proxy in the agent could stop forwarding task heartbeats when an unresponsive upstream connection held a connection-pool slot indefinitely. The proxy client now sets explicit timeouts.

  #### Images included

  See [Astro Remote Execution Agent 1.7.3 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-7-3).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.7.2" description="July 1, 2026">
  #### Additional improvements

  * Updated Agent Client images to include the
    [3.0-16](/docs/runtime/runtime-release-notes#astro-runtime-3-0-16)
    and [3.1-17 Runtime
    versions](/docs/runtime/runtime-release-notes#astro-runtime-3-1-17).

  #### Images included

  See [Astro Remote Execution Agent 1.7.2 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-7-2).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.7.1" description="June 4, 2026">
  #### Additional improvements

  * Added Astro Runtime 3.2-5 to the Agent Client images.
  * Each agent component reports a snapshot of its resolved configuration to the control plane at startup, so you can review the effective settings and how they change over time. Secrets are redacted before the snapshot is sent. Reporting is on by default; set `ASTRO_AGENT_CLIENT_CONFIG_REPORTER_ENABLED=false` to opt out for a component.
  * Removed a blocking call from the worker heartbeat path, reducing task-start latency.
  * The Dag processor heartbeat path now exposes Prometheus metrics, including heartbeat duration, payload size, number of Dags sent, request outcomes, and parse-cache hit rate.
  * The agent now exposes a per-component health gauge on the `/metrics` endpoint, so you can alert on the health of individual components instead of relying only on the Kubernetes probe.
  * Where Sentinel is integrated, the Sentinel dashboard now surfaces Kubernetes Pod events for an unhealthy component, so you can see why a container failed its readiness check.

  #### Bug fixes

  * Fixed a bug where triggers that read connections or variables, for example through `BaseHook.get_connection()` or `Variable.get()`, failed with `ForbiddenSessionUseError`. The Triggerer now proxies connection and variable access through the execution API on all supported runtimes.
  * Fixed Human-in-the-Loop operators on Airflow 3.1 and later, where a deferred trigger could fail authentication when multiple trigger tokens were cached, or fail to parse `datetime` fields in the trigger payload.
  * Fixed a bug where Dag processor callbacks were dropped on Airflow versions before 3.1 because required fields were missing from the heartbeat payload. The agent now backfills these fields.
  * Fixed a bug where a task's reported maximum CPU usage could show an impossibly large value because of a spurious first sample.
  * Where Sentinel is integrated, fixed a bug where a healthy backend could report a misleading message that the agent status was unavailable.

  #### Images included

  See [Astro Remote Execution Agent 1.7.1 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-7-1).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.6.2" description="July 23, 2026">
  #### Additional improvements

  * Updated Agent Client images to include the [3.2-6 Runtime version](/docs/runtime/runtime-release-notes#astro-runtime-3-2-6).
  * Updated bundled dependencies to address security vulnerabilities in `click`, `cryptography`, `pyjwt`, and `python-multipart`.

  #### Images included

  See [Astro Remote Execution Agent 1.6.2 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-6-2).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.6.1" description="June 1, 2026">
  #### Additional improvements

  * JWT redaction now applies inside the isolated task subprocess, so trigger tokens and other JWTs are redacted from agent logs.
  * Updated bundled dependencies to address security vulnerabilities in `cryptography`, `gitpython`, `urllib3`, `python-multipart`, and `mako`.

  #### Bug fixes

  * Fixed a bug where an exception in the heartbeater's run loop, such as a subprocess IPC timeout, could prevent the agent from sending its final terminating heartbeat, leaving the control plane unaware of the shutdown.

  #### Images included

  See [Astro Remote Execution Agent 1.6.1 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-6-1).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.6.0" description="April 16, 2026">
  #### Airflow 3.2 support

  Agent Client now supports Airflow 3.2 (Astro Runtime 3.2-1), including Python 3.13 and 3.14 compatibility.

  #### Additional improvements

  * OpenTelemetry trace contexts are now propagated to Agent Clients.

  #### Bug fixes

  * Fixed a `ValidationError` when processing callbacks with `dag_run.state` on Airflow versions before 3.0.5.
  * Fixed a bug where the worker heartbeater did not report that the agent was terminating during graceful shutdown, so the control plane was not informed that the agent was draining tasks.
  * Fixed shutdown hangs in IPC socket communication where connected clients or pending write flushes could prevent the agent from shutting down.

  #### Images included

  See [Astro Remote Execution Agent 1.6.0 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-6-0).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.5.3" description="July 23, 2026">
  #### Additional improvements

  * Updated bundled dependencies to address security vulnerabilities in `click`, `cryptography`, `pyjwt`, and `python-multipart`.

  #### Images included

  See [Astro Remote Execution Agent 1.5.3 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-5-3).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.5.2" description="June 1, 2026">
  #### Additional improvements

  * JWT redaction now applies inside the isolated task subprocess, so trigger tokens and other JWTs are redacted from agent logs.
  * Bumped the minimum required version of `apache-airflow-providers-git` to 0.3.1, which is needed for compatibility with Airflow 3.1.7 and later.
  * Updated bundled dependencies to address security vulnerabilities in `cryptography`, `gitpython`, `urllib3`, `python-multipart`, and `pyjwt`.

  #### Bug fixes

  * Fixed a bug where an exception in the heartbeater's run loop, such as a subprocess IPC timeout, could prevent the agent from sending its final terminating heartbeat, leaving the control plane unaware of the shutdown.

  #### Images included

  See [Astro Remote Execution Agent 1.5.2 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-5-2).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.5.1" description="April 15, 2026">
  #### Bug fixes

  * Fixed a bug where the worker heartbeater did not report that the agent was terminating during graceful shutdown, so the control plane was not informed that the agent was draining tasks.
  * Fixed shutdown hangs in IPC socket communication where connected clients or pending write flushes could prevent the agent from shutting down.

  #### Images included

  See [Astro Remote Execution Agent 1.5.1 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-5-1).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.5.0" description="March 24, 2026">
  #### XCom support for Triggerer

  Triggers running in the Triggerer component can now read and write XCom values using the execution API. Each trigger receives a per-trigger JWT token for authenticated access, which is automatically refreshed to prevent expiration during long-running triggers.

  #### Additional improvements

  * Added `gc.freeze()` to the Dag processor to reduce garbage collection overhead and improve memory performance.
  * Updated Agent Client images to include the [3.1-14 Runtime version](/docs/runtime/runtime-release-notes#astro-runtime-3-1-14).
  * Unknown settings from configuration sources now produce a warning instead of causing a validation error.
  * The Dag processor and the worker each send a final heartbeat before shutting down.
  * HTTP(S) proxy environment variables are honored for clients that talk to the Astro API server.
  * SIGTERM handling is consolidated across Agent Client components for more predictable shutdowns.
  * Dag file queue handling was reimplemented, with more efficient behavior when Dag bundles refresh.
  * The Triggerer uses a dedicated heartbeater that is decoupled from the Triggerer subprocess lifecycle, improving heartbeat reliability across process restarts.
  * The Dag processor emits additional debug logging and applies a default timeout when sending messages to the coordinator over IPC.
  * `relative_fileloc` is carried in `DagFileParsingResult` and preserved through the Dag processor coordinator.
  * Callback payloads use the `EmailRequest` shape consistently with Airflow’s models.
  * Secrets masking uses imports that match the Airflow 3.0 package layout.
  * Where Sentinel is integrated, the client supports agent ID tracking and container restart detection.

  #### Bug fixes

  * Fixed a bug where failed triggers could remain in the running set and cause repeated cancel loops.
  * Fixed trigger handling when the task instance was null or missing (including skipping triggers with no task instance on Airflow 3.0 clients).
  * Fixed Triggerer coordinator process termination so subprocesses shut down as intended.
  * Fixed graceful shutdown behavior in edge cases.
  * Fixed the log level used when a process has finished.
  * Fixed email-related callback typing when values are built from API responses.
  * Fixed `DagCallback` behavior on older Airflow versions used with the agent.
  * Fixed a bug where `DagModel.bundle_version` did not update for cached DAGs after bundle changes.
  * Fixed a compatibility issue in the Dag processor where the wrong method was called for adding new files on Airflow 3.0 and 3.1 vs 3.2.
  * Fixed a bug where the Triggerer failed with a `LimitOverrunError` when processing large IPC messages.
  * Fixed a bug where non-serializable trigger event payloads caused Triggerer heartbeat failures.
  * Fixed `Stats` import compatibility across different Airflow 3 versions.
  * Fixed a bug where the Dag processor did not exit on fatal exceptions.
  * Fixed a case where the managed Astro subprocess had already exited but the agent could linger; the agent now exits promptly and cleanly.
  * Fixed uncaught errors in socket listener callbacks so a bad callback does not tear down the listener.
  * Fixed client-side stripping of `triggering_user_name` from callbacks for Airflow below 3.1.2.

  #### Images included

  See [Astro Remote Execution Agent 1.5.0 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-5-0).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.4.0">
  Internal-only release.
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.3.12" description="July 23, 2026">
  #### Additional improvements

  * Updated bundled dependencies to address security vulnerabilities in `click`, `cryptography`, `pyjwt`, and `python-multipart`.

  #### Images included

  See [Astro Remote Execution Agent 1.3.12 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-3-12).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.3.11" description="June 4, 2026">
  #### Additional improvements

  * Updated bundled dependencies to address security vulnerabilities in `cryptography`, `gitpython`, `urllib3`, `python-multipart`, `mako`, and `pyjwt`.

  #### Images included

  See [Astro Remote Execution Agent 1.3.11 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-3-11).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.3.10" description="May 14, 2026">
  #### Additional improvements

  * Bumped the minimum required version of `apache-airflow-providers-git` to 0.3.1, which is needed for compatibility with Airflow 3.1.7 and later.

  #### Bug fixes

  * Fixed a bug where an exception in the heartbeater run loop caused shutdown to skip the final terminating heartbeat, so the control plane wasn't informed that the agent had stopped.

  #### Images included

  See [Astro Remote Execution Agent 1.3.10 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-3-10).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.3.9" description="April 16, 2026">
  #### Bug fixes

  * Fixed a bug where the worker heartbeater did not report that the agent was terminating during graceful shutdown, so the control plane was not informed that the agent was draining tasks.
  * Fixed shutdown hangs in IPC socket communication where connected clients or pending write flushes could prevent the agent from shutting down.

  #### Images included

  See [Astro Remote Execution Agent 1.3.9 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-3-9).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.3.8" description="March 25, 2026">
  #### Bug fixes

  * Fixed a bug where the Triggerer failed with a `LimitOverrunError` when processing large IPC messages.

  #### Images included

  See [Astro Remote Execution Agent 1.3.8 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-3-8).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.3.7" description="March 4, 2026">
  #### Bug fixes

  * Fixed a bug where the Triggerer agent did not exit when receiving a `409 Conflict from the API Server`, which prevented it heartbeating successfully.

  #### Images included

  See [Astro Remote Execution Agent 1.3.7 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-3-7).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.3.6" description="February 18, 2026">
  #### Improvements

  * Small performance and telemetry enhancements to the remote Dag Processor agent.

  #### Images included

  See [Astro Remote Execution Agent 1.3.6 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-3-6).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.3.5" description="February 13, 2026">
  #### Bug fixes

  * Fixed a bug where agents shutting down didn't always correctly notify the Astro APIs, which could result in new containers being unable to register.
  * Fixed a bug where the remote Dag Processor agent wouldn't crash after a fatal exception. (In this case crashing was expected and required to allow the agent to re-register successfully.)

  #### Images included

  See [Astro Remote Execution Agent 1.3.5 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-3-5).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.3.4" description="February 5, 2026">
  #### Bug fixes

  * Fixed a bug where agents don't shutdown gracefully on SIGTERM. Worker agents now wait for running tasks to finish before shutting down or until the Pod's termination grace period expires. This fix addresses issues with running tasks being killed when an agent is terminated.

  #### Images included

  See [Astro Remote Execution Agent 1.3.4 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-3-4).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.3.3" description="January 30, 2026">
  <Warning>
    Agent Client versions 1.3.2 and 1.3.3 don't handle SIGTERM gracefully. Running tasks may fail when terminating agents on these versions. This issue is fixed in Agent Client version 1.3.4, which is included in the Astro Remote Execution Agent and Sentinel 1.3.4 release.
  </Warning>

  #### Bug fixes

  * Fixed a bug that could prevent Dag import errors from being cleared when fixed, affecting Airflow ≥ 3.1.6.

  #### Images included

  See [Astro Remote Execution Agent 1.3.3 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-3-3).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.3.2" description="January 30, 2026">
  <Warning>
    Agent Client versions 1.3.2 and 1.3.3 don't handle SIGTERM gracefully. Running tasks may fail when terminating agents on these versions. This issue is fixed in Agent Client version 1.3.4, which is included in the Astro Remote Execution Agent and Sentinel 1.3.4 release.
  </Warning>

  #### Proxy server support

  Agent Client now supports running behind an HTTP(S) proxy server. You can configure proxy settings using the usual `HTTP_PROXY`/`HTTPS_PROXY`/`NO_PROXY` environment variables.

  #### Additional improvements

  * Updated Agent Client images to use the [3.1-11 Runtime version](/docs/runtime/runtime-release-notes#astro-runtime-3-1-11).

  #### Bug fixes

  * Fixed a bug where agents wouldn't terminate correctly if interrupted during initialization.

  #### Images included

  See [Astro Remote Execution Agent 1.3.2 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-3-2).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.3.1" description="January 28, 2026">
  #### Additional improvements

  * Added support for Asset Watcher and Deadline Alert triggers in Airflow 3.1.

  #### Bug fixes

  * Fixed a bug where failed triggers weren't correctly removed from the list of triggers running in a triggerer agent.
  * Fixed a bug where the same trigger could be started multiple times in the same triggerer agent.
  * Fixed a bug affecting execution of callbacks on the Dag Processor in Airflow ≥ 3.1.1.
  * Fixed some nil pointer reference bugs in the Helm chart templates.
  * Fixed an issue where environment variables provided in `commonEnv` weren't able to override the defaults in the Helm chart.

  #### Images included

  See [Astro Remote Execution Agent 1.3.1 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-3-1).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.3.0" description="January 28, 2026">
  #### Bug fixes

  * Fixed a bug where an agent could get stuck in a "cordoned" state indefinitely when temporarily partitioned from the API server. Agents in this state will now detect the situation and recover automatically.

  #### Images included

  See [Astro Remote Execution Agent 1.3.0 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-3-0).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.2.3" description="January 28, 2026">
  #### Additional improvements

  * Added support for Asset Watcher and Deadline Alert triggers in Airflow 3.1.
  * Added support for setting default values for `image` and `imagePullPolicy` that apply to all Agent components in the Helm chart.

  #### Bug fixes

  * Fixed a bug where failed triggers weren't correctly removed from the list of triggers running in a triggerer agent.
  * Fixed a bug where the same trigger could be started multiple times in the same triggerer agent.
  * Fixed a bug affecting execution of callbacks on the Dag Processor in Airflow ≥ 3.1.1.
  * Fixed some nil pointer reference bugs in the Helm chart templates.
  * Fixed an issue where environment variables provided in `commonEnv` weren't able to override the defaults in the Helm chart.

  #### Images included

  See [Astro Remote Execution Agent 1.2.3 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-2-3).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.2.2" description="December 9, 2025">
  #### Additional improvements

  * Moved vector logging sidecar to be part of the init container, so that it keeps running throughout the lifecycle of the Pod and doesn't terminate before the main Agent component container.
  * Added support for configuring `imagePullPolicy` in the Helm chart.
  * Updated Agent Client images to use the [3.1-7 Runtime version](/docs/runtime/runtime-release-notes#astro-runtime-3-1-7).

  #### Bug fixes

  * Fixed a bug in the Helm chart that prevented Worker component resources from being created correctly when multiple workers were configured.
  * Don't specify `worker.replicas` when `worker.hpa.enabled` is set to true in the Helm chart.
  * Fixed typo with using lowercase key `value` as part of `worker.hpa.metrics` in the Helm chart.
  * Report both running and creating triggers in the `running_triggers` part of the triggerer response to prevent starting a trigger with a given ID if it is already running or creating.

  #### Images included

  See [Astro Remote Execution Agent 1.2.2 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-2-2).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.2.1" description="November 17, 2025">
  #### Additional improvements

  * Updated Agent Client images to use the [3.1-4 Runtime version](/docs/runtime/runtime-release-notes#astro-runtime-3-1-4).

  #### Bug fixes

  * Fixed incorrect timestamp values for Dag parsing stats in the Airflow UI.
  * Fixed structlog for Agent logging when using 3.0-x Runtime versions.

  #### Images included

  See [Astro Remote Execution Agent 1.2.1 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-2-1).
</Update>

<Update label="Astro Remote Execution Agent and Sentinel 1.2.0" description="November 10, 2025">
  #### Added Sentinel to Remote Execution Agent Helm chart

  Added a new Sentinel service to Remote Execution Agent Helm chart. Sentinel helps collect monitoring datapoints such as Pod, XCom backend and secrets backend statuses and reports them back to API Server. This is an experimental feature to help with Remote Execution Agent monitoring and is turned off by default in the Agent Helm chart. See [Enable Sentinel for monitoring](/docs/astro/remote-agents-sentinel).

  #### Additional improvements

  * Added a check in the Agent Client to avoid breaking the Remote Deployment by running into forward compatibility issues. For example, Agent Client will get back 422 HTTP response code instead of regular heartbeat response if the Airflow version of the Agent Client is higher than that of the Astro Remote Deployment.
  * Added support to configure `imagePullPolicy` in the Remote Agent Helm chart.

  #### Images included

  See [Astro Remote Execution Agent 1.2.0 images included](/docs/astro/agent-images#astro-remote-execution-agent-and-sentinel-1-2-0).
</Update>

<Update label="Astro Remote Execution Agent 1.1.2" description="January 28, 2026">
  #### Additional improvements

  * Added support for Asset Watcher and Deadline Alert triggers in Airflow 3.1.
  * Moved vector logging sidecar to be part of the init container, so that it keeps running throughout the lifecycle of the Pod and doesn't terminate before the main Agent component container.
  * Added support for configuring `imagePullPolicy` in the Helm chart.
  * Added support for setting default values for `image` and `imagePullPolicy` that apply to all Agent components in the Helm chart.

  #### Bug fixes

  * Fixed a bug where failed triggers weren't correctly removed from the list of triggers running in a triggerer agent.
  * Fixed a bug where the same trigger could be started multiple times in the same triggerer agent.
  * Fixed a bug affecting execution of callbacks on the Dag Processor in Airflow ≥ 3.1.1.
  * Fixed a bug in the Helm chart that prevented Worker component resources from being created correctly when multiple workers were configured.
  * Don't specify `worker.replicas` when `worker.hpa.enabled` is set to true in the Helm chart.
  * Fixed typo with using lowercase key `value` as part of `worker.hpa.metrics` in the Helm chart.
  * Fixed some nil pointer reference bugs in the Helm chart templates.
  * Fixed an issue where environment variables provided in `commonEnv` weren't able to override the defaults in the Helm chart.

  #### Images included

  See [Astro Remote Execution Agent 1.1.2 images included](/docs/astro/agent-images#astro-remote-execution-agent-1-1-2).
</Update>

<Update label="Astro Remote Execution Agent 1.1.1" description="November 17, 2025">
  #### Additional improvements

  * Updated Agent Client images to use the [3.1-4 Runtime version](/docs/runtime/runtime-release-notes#astro-runtime-3-1-4).

  #### Images included

  See [Astro Remote Execution Agent 1.1.1 images included](/docs/astro/agent-images#astro-remote-execution-agent-1-1-1).
</Update>

<Update label="Astro Remote Execution Agent 1.1.0" description="September 29, 2025">
  #### Additional improvements

  * Updated Agent Client images to use the [3.1-1 Runtime version](/docs/runtime/runtime-release-notes#astro-runtime-3-1-1).
  * Added support to directly reference the Agent token file in the Helm chart.
  * Added the ability to configure a custom service account and corresponding annotation per Agent component in the Helm chart.

  #### Remote Agent Worker Kubernetes service account change

  The naming convention for the Remote Agent Worker's Kubernetes service account has been updated. Users who have configured IRSA on AWS, Workload Identity on Azure, or GCP will need to annotate the new service account appropriately. In previous releases, the service account name for the Remote Execution Agent worker was `{{ resourceNamePrefix }}-worker`. The default service account name has been updated to `{{ resourceNamePrefix }}-worker-{{ worker.name }}`. `resourceNamePrefix` and `worker.name` are both attributes set in the `values.yaml` file. You can also provide a custom service account, which overrides the default service account name. The custom service account name applies to all workers.

  #### Bug fixes

  * Fixed a bug where the Dag processor process didn't close cleanly on completion.
  * Fixed a bug where the Agent process crashed in the event of heartbeat failures.

  #### Images included

  See [Astro Remote Execution Agent 1.1.0 images included](/docs/astro/agent-images#astro-remote-execution-agent-1-1-0).
</Update>

<Update label="Astro Remote Execution Agent 1.0.4" description="August 21, 2025">
  #### Additional improvements

  * Updated Agent Client images to use the [3.0-8 Runtime version](/docs/runtime/runtime-release-notes#astro-runtime-3-0-8).

  #### Bug fixes

  * Fixed live task logs for Hosted Astro executor Deployments.

  #### Images included

  See [Astro Remote Execution Agent 1.0.4 images included](/docs/astro/agent-images#astro-remote-execution-agent-1-0-4).
</Update>

<Update label="Astro Remote Execution Agent 1.0.3" description="July 15, 2025">
  #### Prevent `airflow_local_settings.py` Execution in Agent Processes

  The Remote Execution Agent process no longer imports `airflow_local_settings.py`. This prevents errors from user-defined settings that rely on dependencies not available in the Remote Execution Agent's isolated environment.

  #### Images included

  See [Astro Remote Execution Agent 1.0.3 images included](/docs/astro/agent-images#astro-remote-execution-agent-1-0-3).
</Update>

<Update label="Astro Remote Execution Agent 1.0.2" description="July 3, 2025">
  #### Support for Custom Service Accounts and Annotations

  The Remote Execution Agent Helm chart now supports setting custom service account names and annotations for the Worker, Triggerer, and Dag processor components. This allows you to:

  * Bring your own service accounts (BYO-SA) and disable the Helm-managed service account creation
  * Add annotations, such as for AWS IRSA

  This update supports restricted or self-managed environments where service accounts and roles are centrally controlled.

  #### Bug fixes

  * Changed working directory for Remote Execution Agent images to `/usr/local/airflow`
    The workdir for Remote Execution Agent images has moved from `/opt/astro` to `/usr/local/airflow` to align with Runtime images. If you have added a manual `WORKDIR /usr/local/airflow` directive in your image builds you can now remove this if building from the 1.0.2 base images.

  <Warning>
    **Breaking Change**

    If you reference `/opt/astro` in your Dockerfile for a Remote Execution mode Deployment, you must update those references to `/usr/local/airflow`.
  </Warning>

  #### Images included

  See [Astro Remote Execution Agent 1.0.2 images included](/docs/astro/agent-images#astro-remote-execution-agent-1-0-2).

  <Warning>
    Due to a known backwards compatibility issue in Airflow, use 3.0-1 images for Remote Deployments on Runtime 3.0-1, 3.0-2 images for Runtime 3.0-2, and 3.0-4 images for Runtime 3.0-3 and 3.0-4
  </Warning>
</Update>

<Update label="Astro Remote Execution Agent 1.0.1" description="June 2, 2025">
  #### Bug fixes

  * Fixed a bug where the proxy rejected HEAD requests to the XCom API with a `405 Method Not Allowed`. It now correctly supports HEAD requests.

  #### Images included

  See [Astro Remote Execution Agent 1.0.1 images included](/docs/astro/agent-images#astro-remote-execution-agent-1-0-1).

  <Warning>
    Use 3.0-1 Agent images for Remote Deployments using the Astro Runtime/Orchestration Plane 3.0-1 due to an OSS Airflow Bug. You can use 3.0-2 Remote Agent images for any Astro Runtime ≥ 3.0-2.

    See [Upgrade considerations](/docs/astro/agent-maintenance-policy#upgrade-considerations) for more information about the Remote Execution Agent and Astro Runtime version considerations.
  </Warning>
</Update>

<Update label="Astro Remote Execution Agent 1.0.0" description="April 22, 2025">
  #### Introducing the Remote Execution Agent

  With the release of Airflow 3.0, Astro now supports Remote Execution of Dags with the **Astro Remote Execution Agent**. The Remote Execution Agent allows you to keep your sensitive data and execute your Dags in your own environment, while still leveraging Astro features like day zero Airflow Runtime support, observability, and user management. The Astro Remote Execution Agent manages running the Workers, Triggerer, and Dag processors in your environment, while the Airflow Metadata Database, Scheduler, Web/API Server, and Remote Execution API remain in the Astro Orchestration plane.

  See [Remote Execution Agents](/docs/astro/remote-execution-configure-agents) for installation, configuration, and advanced options.

  #### Images included

  See [Astro Remote Execution Agent 1.0.0 images included](/docs/astro/agent-images#astro-remote-execution-agent-1-0-0).

  <Warning>
    Due to a known backwards compatibility issue in Airflow, use 3.0-1 images for Remote Deployments on Runtime 3.0-1, 3.0-2 images for Runtime 3.0-2, and 3.0-4 images for Runtime 3.0-3 and 3.0-4
  </Warning>
</Update>