Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions RELEASE_NOTES.rst
Original file line number Diff line number Diff line change
Expand Up @@ -1756,15 +1756,16 @@ in Airflow 3.0. Run ``airflow --help`` to review the current set of available co
Provider Refactor & Standardization
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Airflow 3.0 completes the migration of several core operators, sensors, and hooks into the new
Airflow 3.0 completes the migration of several core operators, sensors, hooks, and triggers into the new
``apache-airflow-providers-standard`` package. This package now includes commonly used components such as:

- ``PythonOperator``
- ``BashOperator``
- ``EmailOperator``
- ``ShortCircuitOperator``
- ``PythonOperator``, ``BashOperator``
- ``ExternalTaskSensor``, ``FileSensor``
- ``ShortCircuitOperator``, ``LatestOnlyOperator``
- ``SubprocessHook``, ``FilesystemHook``
- ``DateTimeTrigger``, ``TimeDeltaTrigger``, ``FileTrigger``

These operators were previously bundled inside ``airflow-core`` but are now treated as provider-managed components to
These operators, sensors, hooks, and triggers were previously bundled inside ``airflow-core`` but are now treated as provider-managed components to
improve modularity, testability, and lifecycle independence.

This change enables more consistent versioning across providers and prepares Airflow for a future where all integrations
Expand Down
2 changes: 1 addition & 1 deletion airflow-core/docs/installation/upgrading_to_airflow3.rst
Original file line number Diff line number Diff line change
Expand Up @@ -187,7 +187,7 @@ code import Airflow components correctly in Airflow 3. The older paths are depre
Step 4: Install the Standard Provider
--------------------------------------

- Some of the commonly used Operators which were bundled as part of the ``airflow-core`` package (for example ``BashOperator`` and ``PythonOperator``)
- Some of the commonly used Operators, Sensors, and Triggers which were bundled as part of the ``airflow-core`` package (for example ``BashOperator``, ``PythonOperator``, ``ExternalTaskSensor``, ``FileSensor``, etc.)
have now been split out into a separate package: ``apache-airflow-providers-standard``.
- For convenience, this package can also be installed on Airflow 2.x versions, so that Dags can be modified to reference these Operators from the standard provider
package instead of Airflow Core.
Expand Down
4 changes: 3 additions & 1 deletion airflow-core/docs/operators-and-hooks-ref.rst
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,9 @@
Operators and Hooks Reference
=============================

Here's the list of the operators and hooks which are available in this release in the ``apache-airflow`` package.
Here's the list of the operators and hooks which are available in this release.

Note that commonly used operators and sensors (such as ``BashOperator``, ``PythonOperator``, ``ExternalTaskSensor``, etc.) are provided by the ``apache-airflow-providers-standard`` package.

Airflow has many more integrations available for separate installation as
:doc:`apache-airflow-providers:index`.
Expand Down
5 changes: 0 additions & 5 deletions generated/PYPI_README.md
Original file line number Diff line number Diff line change
Expand Up @@ -120,11 +120,6 @@ While it is possible to install Airflow with tools like [Poetry](https://python-
`pip` - especially when it comes to constraint vs. requirements management.
Installing via `Poetry` or `pip-tools` is not currently supported.

There are known issues with ``bazel`` that might lead to circular dependencies when using it to install
Airflow. Please switch to ``pip`` if you encounter such problems. ``Bazel`` community works on fixing
the problem in `this PR <https://github.com/bazelbuild/rules_python/pull/1166>`_ so it might be that
newer versions of ``bazel`` will handle it.

If you wish to install Airflow using those tools, you should use the constraint files and convert
them to the appropriate format and workflow that your tool requires.

Expand Down
4 changes: 2 additions & 2 deletions reproducible_build.yaml
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
release-notes-hash: a449253a6789334b408e2b28073c9a08
source-date-epoch: 1761610265
release-notes-hash: 978a44fe356da19ff03bf7c1c3b0cd93
source-date-epoch: 1762276637