The GitHub Actions job "Tests AMD" on airflow.git/backport-097ae45-v3-0-test 
has succeeded.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
b99f64e389f125c33a3ca895f11cba30f6d93e29 / N R Navaneet 
<[email protected]>
[v3-0-test] fix(systemd): Update systemd unit files and documentation for 
Airflow 3.0 (#52294)

* docs: update public interface doc to reflect airflow.sdk and AIP-72

- Added a note under "Using Airflow Public Interfaces" to recommend using 
`airflow.sdk` as the official interface from Airflow 3.0.
- Referenced AIP-72 and linked related documentation.
- Encouraged users to prefer REST API and Python Client for integrations.

* Update airflow-core/docs/public-airflow-interface.rst

Great

Co-authored-by: Jarek Potiuk <[email protected]>

* fix(systemd): Update systemd service files and docs for Airflow 3.0

- Updated systemd unit files to support Airflow 3.0 architecture.
- Replaced deprecated `webserver` with `api-server` in ExecStart.
- Added service units for new components: `triggerer`, `dag-processor`, and 
`api-server`.
- Adjusted ExecStart commands to support virtualenv-based deployments.
- Improved documentation (`run-with-systemd.rst`) to clarify service changes, 
virtualenv usage, and installation paths.
- Linked to the updated GitHub `scripts/systemd` directory for latest service 
files.

Tested Airflow 3.0 manually on macOS using virtualenv, confirming correct 
startup behavior for `scheduler`, `api-server`, and `triggerer`.

* fix(systemd): Update systemd service files and docs for Airflow 3.0

* Minor test failure fixes

---------
(cherry picked from commit 097ae4517d06d0fae1ae5890e206fffa7e64c148)

Co-authored-by: N R Navaneet <[email protected]>
Co-authored-by: Jarek Potiuk <[email protected]>

Report URL: https://github.com/apache/airflow/actions/runs/16427099126

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to