srchilukoori commented on issue #67655:
URL: https://github.com/apache/airflow/issues/67655#issuecomment-4567045241

   ## RC Testing Results — apache-airflow-ctl 0.1.5rc1
   
   **Environment:** Ubuntu 24.04 (6.8.0-117-generic), Python 3.12.11, uv 
0.11.16, Breeze (Docker)
   **Date:** 2026-05-28
   
   ```bash
   uv venv /tmp/airflow-ctl-rc1-test --python 3.12
   uv pip install --python /tmp/airflow-ctl-rc1-test/bin/python 
apache-airflow-ctl==0.1.5rc1
   ```
   
   ### CLI smoke test
   
   ```
   $ airflowctl version
   {'airflowctl_version': '0.1.5rc1'}
   ```
   
   ### Breeze unit tests
   
   ```
   breeze testing airflow-ctl-tests --python 3.12
   ```
   
   **Result:** 245 passed, 17 warnings in 8.62s ✅
   
   ### Breeze docs build
   
   ```
   breeze build-docs apache-airflow-ctl --docs-only
   ```
   
   **Result:** Documentation build successful ✅
   
   ### Docs fix verification (PR #67046)
   
   Extracted the source distribution and inspected 
`docs/installation/installing-from-sources.rst`:
   
   ```bash
   pip download apache-airflow-ctl==0.1.5rc1 --no-binary :all: --no-deps -d 
/tmp/sdist
   tar xzf /tmp/sdist/apache_airflow_ctl-0.1.5rc1.tar.gz
   ```
   
   | PR | Fix | Result | Notes |
   |----|-----|--------|-------|
   | #67046 | KEYS URL: `airflowctl/KEYS` → `airflow/KEYS` | ✅ Pass | Line 55: 
corrected URL returns HTTP 200 |
   | #67046 | curl base path: `airflowctl/` → `airflow/airflow-ctl/` | ✅ Pass | 
Lines 148-151: path matches `conf.py` `base_url` |
   | #67046 | Shell variable: mixed names → `ctl_download_dir` | ✅ Pass | Lines 
146-154: all references consistent |
   
   **URL verification:**
   
   | URL | Status |
   |-----|--------|
   | `downloads.apache.org/airflowctl/KEYS` (old, broken) | 404 |
   | `downloads.apache.org/airflow/KEYS` (new, fixed) | 200 ✅ |
   | `downloads.apache.org/airflow/airflow-ctl/` (base dir) | 200 ✅ |
   | `dist.apache.org/repos/dist/dev/airflow/airflow-ctl/0.1.5rc1/` (RC 
artifacts) | 200 ✅ |


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to