apache-airflow-providers-edge3 1.3.1rc1__tar.gz → 1.4.0__tar.gz

{apache_airflow_providers_edge3-1.3.1rc1 → apache_airflow_providers_edge3-1.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: apache-airflow-providers-edge3
-Version: 1.3.1rc1
+Version: 1.4.0
 Summary: Provider package apache-airflow-providers-edge3 for Apache Airflow
 Keywords: airflow-provider,edge3,airflow,integration
 Author-email: Apache Software Foundation <dev@airflow.apache.org>
@@ -20,12 +20,13 @@ Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Classifier: Topic :: System :: Monitoring
-Requires-Dist: apache-airflow>=2.10.0rc1
+Requires-Dist: apache-airflow>=2.10.0
+Requires-Dist: apache-airflow-providers-common-compat>=1.8.0
 Requires-Dist: pydantic>=2.11.0
 Requires-Dist: retryhttp>=1.2.0,!=1.3.0
 Project-URL: Bug Tracker, https://github.com/apache/airflow/issues
-Project-URL: Changelog, https://airflow.staged.apache.org/docs/apache-airflow-providers-edge3/1.3.1/changelog.html
-Project-URL: Documentation, https://airflow.staged.apache.org/docs/apache-airflow-providers-edge3/1.3.1
+Project-URL: Changelog, https://airflow.apache.org/docs/apache-airflow-providers-edge3/1.4.0/changelog.html
+Project-URL: Documentation, https://airflow.apache.org/docs/apache-airflow-providers-edge3/1.4.0
 Project-URL: Mastodon, https://fosstodon.org/@airflow
 Project-URL: Slack Chat, https://s.apache.org/airflow-slack
 Project-URL: Source Code, https://github.com/apache/airflow
@@ -56,7 +57,7 @@ Project-URL: YouTube, https://www.youtube.com/channel/UCSXwxpWZQ7XZ1WL3wqevChA/
 
 Package ``apache-airflow-providers-edge3``
 
-Release: ``1.3.1``
+Release: ``1.4.0``
 
 
 Handle edge workers on remote sites via HTTP(s) connection and orchestrates work over distributed sites.
@@ -81,7 +82,7 @@ This is a provider package for ``edge3`` provider. All classes for this provider
 are in ``airflow.providers.edge3`` python package.
 
 You can find package information and changelog for the provider
-in the `documentation <https://airflow.apache.org/docs/apache-airflow-providers-edge3/1.3.1/>`_.
+in the `documentation <https://airflow.apache.org/docs/apache-airflow-providers-edge3/1.4.0/>`_.
 
 Installation
 ------------
@@ -95,14 +96,34 @@ The package supports the following python versions: 3.10,3.11,3.12,3.13
 Requirements
 ------------
 
-==================  ===================
-PIP package         Version required
-==================  ===================
-``apache-airflow``  ``>=2.10.0``
-``pydantic``        ``>=2.11.0``
-``retryhttp``       ``>=1.2.0,!=1.3.0``
-==================  ===================
+==========================================  ===================
+PIP package                                 Version required
+==========================================  ===================
+``apache-airflow``                          ``>=2.10.0``
+``apache-airflow-providers-common-compat``  ``>=1.8.0``
+``pydantic``                                ``>=2.11.0``
+``retryhttp``                               ``>=1.2.0,!=1.3.0``
+==========================================  ===================
+
+Cross provider package dependencies
+-----------------------------------
+
+Those are dependencies that might be needed in order to use all the features of the package.
+You need to install the specified providers in order to use them.
+
+You can install such cross-provider dependencies when installing from PyPI. For example:
+
+.. code-block:: bash
+
+    pip install apache-airflow-providers-edge3[common.compat]
+
+
+==================================================================================================================  =================
+Dependent package                                                                                                   Extra
+==================================================================================================================  =================
+`apache-airflow-providers-common-compat <https://airflow.apache.org/docs/apache-airflow-providers-common-compat>`_  ``common.compat``
+==================================================================================================================  =================
 
 The changelog for the provider package can be found in the
-`changelog <https://airflow.apache.org/docs/apache-airflow-providers-edge3/1.3.1/changelog.html>`_.
+`changelog <https://airflow.apache.org/docs/apache-airflow-providers-edge3/1.4.0/changelog.html>`_.
 

{apache_airflow_providers_edge3-1.3.1rc1 → apache_airflow_providers_edge3-1.4.0}/README.rst

@@ -23,7 +23,7 @@
 
 Package ``apache-airflow-providers-edge3``
 
-Release: ``1.3.1``
+Release: ``1.4.0``
 
 
 Handle edge workers on remote sites via HTTP(s) connection and orchestrates work over distributed sites.
@@ -48,7 +48,7 @@ This is a provider package for ``edge3`` provider. All classes for this provider
 are in ``airflow.providers.edge3`` python package.
 
 You can find package information and changelog for the provider
-in the `documentation <https://airflow.apache.org/docs/apache-airflow-providers-edge3/1.3.1/>`_.
+in the `documentation <https://airflow.apache.org/docs/apache-airflow-providers-edge3/1.4.0/>`_.
 
 Installation
 ------------
@@ -62,13 +62,33 @@ The package supports the following python versions: 3.10,3.11,3.12,3.13
 Requirements
 ------------
 
-==================  ===================
-PIP package         Version required
-==================  ===================
-``apache-airflow``  ``>=2.10.0``
-``pydantic``        ``>=2.11.0``
-``retryhttp``       ``>=1.2.0,!=1.3.0``
-==================  ===================
+==========================================  ===================
+PIP package                                 Version required
+==========================================  ===================
+``apache-airflow``                          ``>=2.10.0``
+``apache-airflow-providers-common-compat``  ``>=1.8.0``
+``pydantic``                                ``>=2.11.0``
+``retryhttp``                               ``>=1.2.0,!=1.3.0``
+==========================================  ===================
+
+Cross provider package dependencies
+-----------------------------------
+
+Those are dependencies that might be needed in order to use all the features of the package.
+You need to install the specified providers in order to use them.
+
+You can install such cross-provider dependencies when installing from PyPI. For example:
+
+.. code-block:: bash
+
+    pip install apache-airflow-providers-edge3[common.compat]
+
+
+==================================================================================================================  =================
+Dependent package                                                                                                   Extra
+==================================================================================================================  =================
+`apache-airflow-providers-common-compat <https://airflow.apache.org/docs/apache-airflow-providers-common-compat>`_  ``common.compat``
+==================================================================================================================  =================
 
 The changelog for the provider package can be found in the
-`changelog <https://airflow.apache.org/docs/apache-airflow-providers-edge3/1.3.1/changelog.html>`_.
+`changelog <https://airflow.apache.org/docs/apache-airflow-providers-edge3/1.4.0/changelog.html>`_.

{apache_airflow_providers_edge3-1.3.1rc1 → apache_airflow_providers_edge3-1.4.0}/docs/architecture.rst

@@ -60,10 +60,10 @@ deployed outside of the central Airflow cluster is connected via HTTP(s) to the
         edge_worker->api[label="HTTP(s)"]
     }
 
-* **Workers** - Execute the assigned tasks - most standard setup has local or centralized workers, e.g. via Celery
+* **Workers** (Central) - Execute the assigned tasks - most standard setup has local or centralized workers, e.g. via Celery
 * **Edge Workers** - Special workers which pull tasks via HTTP(s) as provided as feature via this provider package
 * **Scheduler** - Responsible for adding the necessary tasks to the queue. The EdgeExecutor is running as a module inside the scheduler.
-* **API server** - HTTP REST API Server provides access to Dag/task status information. The required end-points are
+* **API server** (webserver in Airflow 2.x) - HTTP REST API Server provides access to Dag/task status information. The required end-points are
   provided by the Edge provider plugin. The Edge Worker uses this API to pull tasks and send back the results.
 * **Database** - Contains information about the status of tasks, Dags, Variables, connections, etc.
 
@@ -73,19 +73,18 @@ In detail the parts of the Edge provider are deployed as follows:
    :alt: Overview and communication of Edge Provider modules
 
 * **EdgeExecutor** - The EdgeExecutor is running inside the core Airflow scheduler. It is responsible for
-  scheduling tasks and sending them to the Edge job queue in the database. The EdgeExecutor is a subclass of the
-  ``airflow.executors.base_executor.BaseExecutor`` class. To activate the EdgeExecutor, you need to set the
-  ``executor`` configuration option in the ``airflow.cfg`` file to
+  scheduling tasks and sending them to the Edge job queue in the database. To activate the EdgeExecutor, you
+  need to set the ``executor`` configuration option in the ``airflow.cfg`` file to
   ``airflow.providers.edge3.executors.EdgeExecutor``. For more details see :doc:`edge_executor`. Note that also
   multiple executors can be used in parallel together with the EdgeExecutor.
-* **API server** - The API server is providing REST endpoints to the web UI as well as serves static files. The
-  Edge provider adds a plugin that provides additional REST API for the Edge Worker as well as UI elements to
-  manage workers (currently Airflow 2.10 only).
+* **API server** (webserver in Airflow 2.x) - The API server is providing REST endpoints to the web UI as well
+  as serves static files. The Edge provider adds a plugin that provides additional REST API for the Edge Worker
+  as well as UI elements to manage workers (not available in Airflow 3.0).
   The API server is responsible for handling requests from the Edge Worker and sending back the results. To
   activate the API server, you need to set the ``api_enabled`` configuration option in ``edge`` section in the
   ``airflow.cfg`` file to ``True``. The API endpoints for edge is not started by default.
-  Fr more details see :doc:`ui_plugin`.
-* **Database** - The Airflow meta database is used to store the status of tasks, Dags, Variables, connections
+  For more details see :doc:`ui_plugin`.
+* **Database** - The Airflow meta database is used to store the status of tasks, Dags, Variables, Connections
   etc. The Edge provider uses the database to store the status of the Edge Worker instances and the tasks that
   are assigned to it. The database is also used to store the results of the tasks that are executed by the
   Edge Worker. Setup of needed tables and migration is done automatically when the provider package is deployed.
@@ -174,7 +173,7 @@ The following features are known missing and will be implemented in increments:
   - Test/Support on Windows for Edge Worker
 
 - Scaling test - Check and define boundaries of workers/jobs. Today it is known to
-  scale into a range of 50 workers. This is not a hard limit but just an experience reported.
+  scale into a range of ~80 workers. This is not a hard limit but just an experience reported.
 - Load tests - impact of scaled execution and code optimization
 - Incremental logs during task execution can be served w/o shared log disk on api-server
 - Reduce dependencies during execution: Today the worker depends on the airflow core with a lot

{apache_airflow_providers_edge3-1.3.1rc1 → apache_airflow_providers_edge3-1.4.0}/docs/changelog.rst

@@ -27,6 +27,39 @@
 Changelog
 ---------
 
+1.4.0
+.....
+
+Features
+~~~~~~~~
+
+* ``Introduce generic Callbacks to support running callbacks on executors (#54796)``
+* ``Add revoke_task implementation to EdgeExecutor for task queued timeout support (#56240)``
+
+Bug Fixes
+~~~~~~~~~
+
+* ``Bugfix/remove airflow utils deprecations in edge (#56568)``
+* ``Fix Edge3 provider navigation with webserver base_url configuration (#56189)``
+
+Misc
+~~~~
+
+* ``Migrate edge3 provider to ''common.compat'' (#56998)``
+* ``SQLA2: Partially fix type hints in the edge3 provider (#56873)``
+
+Doc-only
+~~~~~~~~
+
+* ``Correct 'Dag' to 'DAG' for code snippets in provider docs (#56727)``
+* ``Revise details of edge documentation after Airflow 3.1 release (#56166)``
+* ``Remove placeholder Release Date in changelog and index files (#56056)``
+
+.. Below changes are excluded from the changelog. Move them to
+   appropriate section above if needed. Do not delete the lines(!):
+   * ``Common.Compat: Extract reusable compat utilities and rename to sdk (#56884)``
+   * ``Enable PT011 rule to prvoider tests (#56277)``
+
 1.3.1
 .....
 
@@ -48,8 +81,6 @@ Misc
 .....
 
 
-Release Date: ``|PypiReleaseDate|``
-
 Features
 ~~~~~~~~
 
@@ -88,8 +119,6 @@ Doc-only
 1.2.0
 .....
 
-Release Date: ``|PypiReleaseDate|``
-
 Features
 ~~~~~~~~
 

{apache_airflow_providers_edge3-1.3.1rc1 → apache_airflow_providers_edge3-1.4.0}/docs/deployment.rst

@@ -21,8 +21,7 @@ Edge Worker Deployment
 Edge Workers can be deployed outside of the central Airflow infrastructure. They
 are connected to the Airflow API server via HTTP(s). The Edge Worker is a
 lightweight component that can be deployed on any machine that has outbound
-HTTP(s) access to the Airflow API server. The Edge Worker is designed to be
-lightweight and easy to deploy. It allows you to run Airflow tasks on machines
+HTTP(s) access to the Airflow API server. It allows you to run Airflow tasks on machines
 that are not part of your main data center, e.g. edge servers. This also allows to
 deploy only reduced dependencies on the edge worker.
 
@@ -46,7 +45,8 @@ Minimum Airflow configuration settings for the Edge Worker to make it running is
 
 - Section ``[api_auth]``
 
-  - ``jwt_secret``: A matching secret to that on the api-server (starting from version 3.0.0).
+  - ``jwt_secret``: A shared secret between workers and the api-server to authenticate
+    (starting from version 3.0.0).
 
 - Section ``[core]``
 
@@ -56,7 +56,7 @@ Minimum Airflow configuration settings for the Edge Worker to make it running is
   - ``executor``: Executor must be set or added to be ``airflow.providers.edge3.executors.EdgeExecutor``
   - ``internal_api_secret_key``: An encryption key must be set on api-server and Edge Worker component as
     shared secret to authenticate traffic. It should be a random string like the fernet key
-    (for versions earlier than 3.0.0).
+    (for versions earlier than 3.0.0 - from Airflow 3.0 and above this is using ``api_auth.jwt_secret``).
 
 - Section ``[edge]``
 
@@ -72,6 +72,20 @@ subcommand
 .. code-block:: bash
 
     airflow edge worker
+    2025-09-27T12:28:32.954316Z [info     ] Starting worker with API endpoint http://localhost:8080/edge_worker/v1/rpcapi
+      ____________       _____________
+     ____    |__( )_________  __/__  /________      __
+    ____  /| |_  /__  ___/_  /_ __  /_  __ \_ | /| / /
+    ___  ___ |  / _  /   _  __/ _  / / /_/ /_ |/ |/ /
+    _/_/  |_/_/  /_/    /_/    /_/  \____/____/|__/
+       ____   __           _      __         __
+      / __/__/ /__ ____   | | /| / /__  ____/ /_____ ____
+     / _// _  / _  / -_)  | |/ |/ / _ \/ __/   _/ -_) __/
+    /___/\_,_/\_, /\__/   |__/|__/\___/_/ /_/\_\\__/_/
+            /___/
+
+    2025-09-27T12:28:33.171525Z [info     ] No new job to process
+
 
 You can also start this worker in the background by running
 it as a daemonized process. Additionally, you can redirect stdout
@@ -97,9 +111,9 @@ process as and wait until all running tasks are completed. Also in a console you
 ``Ctrl-C`` to stop the worker.
 
 If you want to monitor the remote activity and worker, use the UI plugin which
-is included in the provider package and install it on the webserver and use the
+is included in the provider package and install it on the api-server / webserver and use the
 "Admin" - "Edge Worker Hosts" and "Edge Worker Jobs" pages.
-(Note: The plugin is not ported to Airflow 3.0 web UI at time of writing)
+(Note: The plugin is not available on Airflow 3.0 UI, it is only in 2.x and 3.1++)
 
 If you want to check status of the worker via CLI you can use the command
 

{apache_airflow_providers_edge3-1.3.1rc1 → apache_airflow_providers_edge3-1.4.0}/docs/edge_executor.rst

@@ -27,6 +27,9 @@ The configuration parameters of the Edge Executor can be found in the Edge provi
 
 To understand the setup of the Edge Executor, please also take a look to :doc:`architecture`.
 
+ See more details Airflow documentation
+  :ref:`apache-airflow:using-multiple-executors-concurrently`.
+
 .. _edge_executor:queue:
 
 Queues
@@ -43,6 +46,7 @@ Workers can listen to one or multiple queues of tasks. When a worker is
 started (using command ``airflow edge worker``), a set of comma-delimited queue
 names (with no whitespace) can be given (e.g. ``airflow edge worker -q remote,wisconsin_site``).
 This worker will then only pick up tasks wired to the specified queue(s).
+If the ``queue`` attribute is not given then a worker will pick tasks from all queues.
 
 This can be useful if you need specialized workers, either from a
 resource perspective (for say very lightweight tasks where one worker
@@ -80,12 +84,12 @@ Here is an example setting pool_slots for a task:
 
     import pendulum
 
-    from airflow import Dag
+    from airflow import DAG
     from airflow.decorators import task
     from airflow.example_dags.libs.helper import print_stuff
     from airflow.settings import AIRFLOW_HOME
 
-    with Dag(
+    with DAG(
         dag_id="example_edge_pool_slots",
         schedule=None,
         start_date=pendulum.datetime(2021, 1, 1, tz="UTC"),
@@ -104,9 +108,10 @@ Current Limitations Edge Executor
 
 - Some known limitations
 
-  - Log upload will only work if you use a single web server instance or they need to share one log file volume.
-    Logs are uploaded in chunks and are transferred via API. If you use multiple webservers w/o a shared log volume
-    the logs will be scattered across the webserver instances.
+  - Log upload will only work if you use a single api-server / webserver instance or they need to share one log file
+    volume. Logs are uploaded in chunks and are transferred via API. If you use multiple api-servers / webservers w/o
+    a shared log volume the logs will be scattered across the api-server / webserver instances and if you view the
+    logs on UI you will only see fractions of the logs.
   - Performance: No extensive performance assessment and scaling tests have been made. The edge executor package is
     optimized for stability. This will be incrementally improved in future releases. Setups have reported stable
-    operation with ~80 workers until now. Note that executed tasks require more webserver API capacity.
+    operation with ~80 workers until now. Note that executed tasks require more api-server / webserver API capacity.

{apache_airflow_providers_edge3-1.3.1rc1 → apache_airflow_providers_edge3-1.4.0}/docs/index.rst

@@ -90,7 +90,7 @@ Additional REST API endpoints are provided to distribute tasks and manage the ed
 are provided by the API server.
 
 
-Release: 1.3.1
+Release: 1.4.0
 
 Provider package
 ----------------
@@ -110,10 +110,39 @@ Requirements
 
 The minimum Apache Airflow version supported by this provider distribution is ``2.10.0``.
 
-==================  ===================
-PIP package         Version required
-==================  ===================
-``apache-airflow``  ``>=2.10.0``
-``pydantic``        ``>=2.11.0``
-``retryhttp``       ``>=1.2.0,!=1.3.0``
-==================  ===================
+==========================================  ===================
+PIP package                                 Version required
+==========================================  ===================
+``apache-airflow``                          ``>=2.10.0``
+``apache-airflow-providers-common-compat``  ``>=1.8.0``
+``pydantic``                                ``>=2.11.0``
+``retryhttp``                               ``>=1.2.0,!=1.3.0``
+==========================================  ===================
+
+Cross provider package dependencies
+-----------------------------------
+
+Those are dependencies that might be needed in order to use all the features of the package.
+You need to install the specified provider distributions in order to use them.
+
+You can install such cross-provider dependencies when installing from PyPI. For example:
+
+.. code-block:: bash
+
+    pip install apache-airflow-providers-edge3[common.compat]
+
+
+==================================================================================================================  =================
+Dependent package                                                                                                   Extra
+==================================================================================================================  =================
+`apache-airflow-providers-common-compat <https://airflow.apache.org/docs/apache-airflow-providers-common-compat>`_  ``common.compat``
+==================================================================================================================  =================
+
+Downloading official packages
+-----------------------------
+
+You can download officially released packages and verify their checksums and signatures from the
+`Official Apache Download site <https://downloads.apache.org/airflow/providers/>`_
+
+* `The apache-airflow-providers-edge3 1.4.0 sdist package <https://downloads.apache.org/airflow/providers/apache_airflow_providers_edge3-1.4.0.tar.gz>`_ (`asc <https://downloads.apache.org/airflow/providers/apache_airflow_providers_edge3-1.4.0.tar.gz.asc>`__, `sha512 <https://downloads.apache.org/airflow/providers/apache_airflow_providers_edge3-1.4.0.tar.gz.sha512>`__)
+* `The apache-airflow-providers-edge3 1.4.0 wheel package <https://downloads.apache.org/airflow/providers/apache_airflow_providers_edge3-1.4.0-py3-none-any.whl>`_ (`asc <https://downloads.apache.org/airflow/providers/apache_airflow_providers_edge3-1.4.0-py3-none-any.whl.asc>`__, `sha512 <https://downloads.apache.org/airflow/providers/apache_airflow_providers_edge3-1.4.0-py3-none-any.whl.sha512>`__)

{apache_airflow_providers_edge3-1.3.1rc1 → apache_airflow_providers_edge3-1.4.0}/docs/ui_plugin.rst

@@ -22,7 +22,7 @@ The Edge provider uses a Plugin to
 
 - Extend the REST API endpoints for connecting workers to the Airflow cluster
 - Provide a web UI for managing the workers and monitoring their status and tasks
-  (Note: Airflow 3.0 does not have support for UI plugins. The UI plugin is only available in Airflow 2.10 and in 3.1 and newer.)
+  (Note: Airflow 3.0 does not have support for UI plugins. The UI plugin is only available in Airflow 2.x and in 3.1 and newer.)
 
 REST API endpoints
 ------------------
@@ -35,14 +35,14 @@ The Edge provider adds the following REST API endpoints to the Airflow API:
 - ``/edge_worker/v1/health``: Check that the API endpoint is deployed and active
 
 To see full documentation of the API endpoints open the Airflow web UI and navigate to
-the sub-path ``/edge_worker/docs`` (Airflow 3.0) or ``/edge_worker/v1/ui`` (Airflow 2.10).
+the sub-path ``/edge_worker/docs`` (Airflow 3.0) or ``/edge_worker/v1/ui`` (Airflow 2.x).
 
 Web UI Plugin
 -------------
 
 .. note::
 
-    Airflow 3.0 does not support UI plugins. The UI plugin is only available in Airflow 2.10 and in 3.1 and newer.
+    Airflow 3.0 does not support UI plugins. The UI plugin is only available in Airflow 2.x and in 3.1 and newer.
     Alternatively you can use the CLI commands as described in :ref:`deployment:maintenance-mgmt-cli`.
 
 The Edge provider adds a web UI plugin to the Airflow web UI. The plugin is

{apache_airflow_providers_edge3-1.3.1rc1 → apache_airflow_providers_edge3-1.4.0}/provider.yaml

@@ -33,13 +33,14 @@ description: |
   are provided by the API server.
 
 state: ready
-source-date-epoch: 1758734943
+source-date-epoch: 1761116659
 
 # Note that those versions are maintained by release manager - do not update them manually
 # with the exception of case where other provider in sources has >= new provider version.
 # In such case adding >= NEW_VERSION and bumping to NEW_VERSION in a provider have
 # to be done in the same PR
 versions:
+  - 1.4.0
   - 1.3.1
   - 1.3.0
   - 1.2.0

{apache_airflow_providers_edge3-1.3.1rc1 → apache_airflow_providers_edge3-1.4.0}/pyproject.toml

@@ -25,7 +25,7 @@ build-backend = "flit_core.buildapi"
 
 [project]
 name = "apache-airflow-providers-edge3"
-version = "1.3.1rc1"
+version = "1.4.0"
 description = "Provider package apache-airflow-providers-edge3 for Apache Airflow"
 readme = "README.rst"
 authors = [
@@ -57,7 +57,8 @@ requires-python = ">=3.10"
 # Make sure to run ``prek update-providers-dependencies --all-files``
 # After you modify the dependencies, and rebuild your Breeze CI image with ``breeze ci-image build``
 dependencies = [
-    "apache-airflow>=2.10.0rc1",
+    "apache-airflow>=2.10.0",
+    "apache-airflow-providers-common-compat>=1.8.0",
     "pydantic>=2.11.0",
     "retryhttp>=1.2.0,!=1.3.0",
 ]
@@ -67,6 +68,7 @@ dev = [
     "apache-airflow",
     "apache-airflow-task-sdk",
     "apache-airflow-devel-common",
+    "apache-airflow-providers-common-compat",
     # Additional devel dependencies (do not remove this line and add extra development dependencies)
 ]
 
@@ -96,8 +98,8 @@ apache-airflow-providers-common-sql = {workspace = true}
 apache-airflow-providers-standard = {workspace = true}
 
 [project.urls]
-"Documentation" = "https://airflow.staged.apache.org/docs/apache-airflow-providers-edge3/1.3.1"
-"Changelog" = "https://airflow.staged.apache.org/docs/apache-airflow-providers-edge3/1.3.1/changelog.html"
+"Documentation" = "https://airflow.apache.org/docs/apache-airflow-providers-edge3/1.4.0"
+"Changelog" = "https://airflow.apache.org/docs/apache-airflow-providers-edge3/1.4.0/changelog.html"
 "Bug Tracker" = "https://github.com/apache/airflow/issues"
 "Source Code" = "https://github.com/apache/airflow"
 "Slack Chat" = "https://s.apache.org/airflow-slack"

{apache_airflow_providers_edge3-1.3.1rc1 → apache_airflow_providers_edge3-1.4.0}/src/airflow/providers/edge3/__init__.py

@@ -29,7 +29,7 @@ from airflow import __version__ as airflow_version
 
 __all__ = ["__version__"]
 
-__version__ = "1.3.1"
+__version__ = "1.4.0"
 
 if packaging.version.parse(packaging.version.parse(airflow_version).base_version) < packaging.version.parse(
     "2.10.0"

{apache_airflow_providers_edge3-1.3.1rc1 → apache_airflow_providers_edge3-1.4.0}/src/airflow/providers/edge3/cli/worker.py

@@ -34,6 +34,7 @@ from requests import HTTPError
 
 from airflow import __version__ as airflow_version
 from airflow.configuration import conf
+from airflow.providers.common.compat.sdk import timezone
 from airflow.providers.edge3 import __version__ as edge_provider_version
 from airflow.providers.edge3.cli.api_client import (
     jobs_fetch,
@@ -52,7 +53,6 @@ from airflow.providers.edge3.cli.signalling import (
 )
 from airflow.providers.edge3.models.edge_worker import EdgeWorkerState, EdgeWorkerVersionException
 from airflow.providers.edge3.version_compat import AIRFLOW_V_3_0_PLUS
-from airflow.utils import timezone
 from airflow.utils.net import getfqdn
 from airflow.utils.state import TaskInstanceState
 

{apache_airflow_providers_edge3-1.3.1rc1 → apache_airflow_providers_edge3-1.4.0}/src/airflow/providers/edge3/example_dags/win_test.py

@@ -67,7 +67,7 @@ if TYPE_CHECKING:
 try:
     from airflow.operators.python import PythonOperator
 except ImportError:
-    from airflow.providers.common.compat.standard.operators import PythonOperator
+    from airflow.providers.common.compat.standard.operators import PythonOperator  # type: ignore[no-redef]
 
 
 class CmdOperator(BaseOperator):

{apache_airflow_providers_edge3-1.3.1rc1 → apache_airflow_providers_edge3-1.4.0}/src/airflow/providers/edge3/executors/edge_executor.py

@@ -31,13 +31,13 @@ from airflow.cli.cli_config import GroupCommand
 from airflow.configuration import conf
 from airflow.executors.base_executor import BaseExecutor
 from airflow.models.taskinstance import TaskInstance, TaskInstanceState
+from airflow.providers.common.compat.sdk import timezone
 from airflow.providers.edge3.cli.edge_command import EDGE_COMMANDS
 from airflow.providers.edge3.models.edge_job import EdgeJobModel
 from airflow.providers.edge3.models.edge_logs import EdgeLogsModel
 from airflow.providers.edge3.models.edge_worker import EdgeWorkerModel, EdgeWorkerState, reset_metrics
 from airflow.providers.edge3.version_compat import AIRFLOW_V_3_0_PLUS
 from airflow.stats import Stats
-from airflow.utils import timezone
 from airflow.utils.db import DBLocks, create_global_lock
 from airflow.utils.session import NEW_SESSION, provide_session
 
@@ -352,7 +352,7 @@ class EdgeExecutor(BaseExecutor):
                         del self.last_reported_state[job.key]
                     self.fail(job.key)
                 else:
-                    self.last_reported_state[job.key] = job.state
+                    self.last_reported_state[job.key] = TaskInstanceState(job.state)
             if (
                 job.state == TaskInstanceState.SUCCESS
                 and job.last_update_t < (datetime.now() - timedelta(minutes=job_success_purge)).timestamp()
@@ -399,6 +399,35 @@ class EdgeExecutor(BaseExecutor):
     def terminate(self):
         """Terminate the executor is not doing anything."""
 
+    @provide_session
+    def revoke_task(self, *, ti: TaskInstance, session: Session = NEW_SESSION):
+        """
+        Revoke a task instance from the executor.
+
+        This method removes the task from the executor's internal state and deletes
+        the corresponding EdgeJobModel record to prevent edge workers from picking it up.
+
+        :param ti: Task instance to revoke
+        :param session: Database session
+        """
+        # Remove from executor's internal state
+        self.running.discard(ti.key)
+        self.queued_tasks.pop(ti.key, None)
+        if ti.key in self.last_reported_state:
+            del self.last_reported_state[ti.key]
+
+        # Delete the job from the database to prevent edge workers from picking it up
+        session.execute(
+            delete(EdgeJobModel).where(
+                EdgeJobModel.dag_id == ti.dag_id,
+                EdgeJobModel.task_id == ti.task_id,
+                EdgeJobModel.run_id == ti.run_id,
+                EdgeJobModel.map_index == ti.map_index,
+                EdgeJobModel.try_number == ti.try_number,
+            )
+        )
+        self.log.info("Revoked task instance %s from EdgeExecutor", ti.key)
+
     def try_adopt_task_instances(self, tis: Sequence[TaskInstance]) -> Sequence[TaskInstance]:
         """
         Try to adopt running task instances that have been abandoned by a SchedulerJob dying.