apache · shahar1 · May 5, 2026 · May 4, 2026 · May 5, 2026
@@ -0,0 +1,9 @@
+<!-- SPDX-License-Identifier: Apache-2.0
+     https://www.apache.org/licenses/LICENSE-2.0 -->
+
+# Arabic (`ar`) translation guidelines
+
+No locale-specific guidance has been authored yet for Arabic. Until this file
+is filled in, follow the global rules in the parent
+[airflow-translations SKILL.md](../SKILL.md). Contributions to this guide are
+welcome.
@@ -0,0 +1,9 @@
+<!-- SPDX-License-Identifier: Apache-2.0
+     https://www.apache.org/licenses/LICENSE-2.0 -->
+
+# Italian (`it`) translation guidelines
+
+No locale-specific guidance has been authored yet for Italian. Until this file
+is filled in, follow the global rules in the parent
+[airflow-translations SKILL.md](../SKILL.md). Contributions to this guide are
+welcome.
@@ -0,0 +1,9 @@
+<!-- SPDX-License-Identifier: Apache-2.0
+     https://www.apache.org/licenses/LICENSE-2.0 -->
+
+# Turkish (`tr`) translation guidelines
+
+No locale-specific guidance has been authored yet for Turkish. Until this file
+is filled in, follow the global rules in the parent
+[airflow-translations SKILL.md](../SKILL.md). Contributions to this guide are
+welcome.
@@ -112,6 +112,8 @@ recover from.
 
 ---
 
+<a id="mark-ready"></a>
+
 ## `mark-ready` — add `ready for maintainer review` label
 
 **Mandatory pre-mutation check.** Before adding the label, the
@@ -160,6 +162,8 @@ error; this is the only action of the skill whose sole purpose
 
 ---
 
+<a id="mark-ready-with-ping"></a>
+
 ## `mark-ready-with-ping` — promote a likely-addressed PR + ping reviewers
 
 A composite of `mark-ready` plus a `ping` comment. Used when

diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
@@ -400,6 +400,35 @@ repos:
         files: ^\.github/workflows/.*$|^\.github/actions/.*$
         require_serial: true
         entry: zizmor
+  - repo: https://github.com/lycheeverse/lychee
+    rev: e85aaf5524b2f808e63bae55e594c843220f10f2  # frozen: lychee-v0.24.2
+    hooks:
+      # Use the upstream `lychee-docker` variant rather than the script-based
+      # `lychee` hook because the prebuilt lychee binaries that the script
+      # downloads are linked against newer glibc than ubuntu-22.04 runners
+      # ship with (`GLIBC_2.38` / `GLIBC_2.39` not found at runtime). The
+      # docker variant runs the official `lycheeverse/lychee` image, which
+      # bundles its own libc and is portable across runners.
+      - id: lychee-docker
+        name: Check internal Markdown links with lychee (offline mode)
+        description: >-
+          Validate intra-repo links in Markdown files (relative paths, anchors,
+          and fragments) without making any HTTP requests. Auto-generated client
+          docs are excluded because they are regenerated from OpenAPI specs.
+        types: [markdown]
+        args:
+          - --offline
+          - --no-progress
+          - --root-dir
+          - .
+          - --include-fragments
+        exclude: |
+          (?x)
+          ^clients/python/|
+          ^.*/openapi-gen/|
+          ^.*/node_modules/|
+          ^\.build/|
+          ^generated/
   - repo: local
     # Note that this is the 2nd "local" repo group in the .pre-commit-config.yaml file. This is because
     # we try to minimize the number of passes that must happen to apply some of the changes

diff --git a/airflow-core/src/airflow/_shared/AGENTS.md b/airflow-core/src/airflow/_shared/AGENTS.md
@@ -5,7 +5,7 @@
 # The `_shared` package — Agent Instructions
 
 Each shared library is a symbolic link to the library package sources from the shared library
-located in the [shared folder](../../shared). In the shared folder each library is a separate
+located in the [shared folder](../../../../shared). In the shared folder each library is a separate
 distribution that has it's own tests and dependencies. Those dependencies and links to those
 libraries are maintained by `prek` hook automatically.
 

diff --git a/airflow-core/src/airflow/_shared/README.md b/airflow-core/src/airflow/_shared/README.md
@@ -32,4 +32,4 @@ library code is stored in "shared" folder) - and at the same time we can have di
 same shared library in different packages when for example `airflow-core` and `task-sdk` package are
 installed together in different version.
 
-You can read about it in [the shared README.md](../../shared/README.md) document.
+You can read about it in [the shared README.md](../../../../shared/README.md) document.
@@ -62,7 +62,7 @@ Adding a new Execution API feature touches multiple packages. All of these must
 - Dag processor handler: `airflow-core/src/airflow/dag_processing/processor.py`
 - Triggerer handler: `airflow-core/src/airflow/jobs/triggerer_job_runner.py`
 - Task SDK generated models: `task-sdk/src/airflow/sdk/api/datamodels/_generated.py`
-- Full versioning guide: [`contributing-docs/19_execution_api_versioning.rst`](../../../../contributing-docs/19_execution_api_versioning.rst)
+- Full versioning guide: [`contributing-docs/19_execution_api_versioning.rst`](../../../../../contributing-docs/19_execution_api_versioning.rst)
 
 ## Token Scope Infrastructure
 

@@ -161,7 +161,7 @@ When submitting a PR that adds new E2E coverage, briefly explain in the PR descr
 
 2. **Create a spec file** in `specs/`
    - Import page objects and write test steps
-   - See existing test: [dag-trigger.spec.ts](specs/dag-trigger.spec.ts)
+   - See existing test: [dag-runs.spec.ts](specs/dag-runs.spec.ts)
 
 3. **Run tests locally**
 

@@ -202,7 +202,7 @@ EOF
 When it is time to cut the RC, you should:
 
 1. Generate an additional completeness output:
-  a. If there are incomplete locales that were also incomplete in the previous major/minor release, please contact the code owner and ask them to act according to the [removing or replacing ownership procedure](../airflow-core/src/airflow/ui/public/i18n/README.md#removing-or-replacing-ownership) in the i18n policy.
+  a. If there are incomplete locales that were also incomplete in the previous major/minor release, please contact the code owner and ask them to act according to the [Relinquishing translation/code ownership procedure](../airflow-core/src/airflow/ui/public/i18n/README.md#relinquishing-translationcode-ownership) in the i18n policy.
   b. If there are other incomplete locales, please write it as a reminder for the next major/minor release.
 2. Post the final completeness output on the same thread.
 

@@ -204,7 +204,7 @@ The minimum version of Kubernetes should be updated according to
 https://github.com/apache/airflow/blob/main/README.md#requirements in two places:
 
 * [../../helm-chart/README.md](../chart/README.md)
-* [../docs/helm-chart/index.rst](../docs/helm-chart/index.rst)
+* [../chart/docs/index.rst](../chart/docs/index.rst)
 
 
 ## Build RC artifacts

@@ -108,7 +108,7 @@ it uses the latest installed version of airflow and providers. However,
 you can choose different installation methods as described in [Building
 PROD docker images from released PIP packages](#building-prod-docker-images-from-released-pip-packages). Detailed
 reference for building production image from different sources can be
-found in: [Build Args reference](../../../../docs/docker-stack/build-arg-ref.rst#installing-airflow-using-different-methods)
+found in: [Build Args reference](../../../../docker-stack-docs/build-arg-ref.rst#installing-airflow-using-different-methods)
 
 You can build the CI image using current sources this command:
 

@@ -25,14 +25,13 @@ Small tool to update status of all AIP-47 issues.
 
 Simply:
 
-1) Activate dev environment based on [requirements](../../dev/requirements.txt)
+1) Set `GITHUB_TOKEN` to a repo-writeable token.
 
-2) Set GITHUB_TOKEN to repo-writeable token
-
-3) Run this:
+2) Run the script via `uv` (it pulls in the few third-party deps it
+   needs — `PyGithub`, `rich-click`, `rich`):
 
 ```bash
-python dev/system_tests/update_issue_status.py
+uv run --with PyGithub --with rich-click --with rich python dev/system_tests/update_issue_status.py
 ```