inchang-ing opened a new pull request, #76361:
URL: https://github.com/apache/airflow/pull/76361

   The Bluesky entry in the published package metadata points at 
`apache-airflow.bsky.social`, a handle Bluesky does not resolve, so the link on 
the PyPI project page and in the release announcement templates leads nowhere. 
The project account moved to `airflow.apache.org`, which is the handle the 
project now publishes everywhere else.
   
   This updates that one url in the nine places it appears, the five 
`pyproject.toml` project url tables and the four release templates under 
`dev/`. Nothing else in those files changes.
   
   ##### How the new handle was confirmed
   
   The change to `airflow.apache.org` is announced on the project mailing list, 
thread "Bluesky Acocunt changed to @airflow.apache.org" 
(https://lists.apache.org/thread/kp1v57g3qcbfslwb4n7dk31ln1xywv1d), and the 
project Mastodon profile at `https://fosstodon.org/@airflow` lists 
`https://bsky.app/profile/airflow.apache.org` in its profile fields. `bsky.app` 
is not reachable from the machine this was prepared on, so the profile itself 
could not be fetched to confirm resolution directly, the two published 
references above are what the change rests on.
   
   The five `pyproject.toml` files were re-parsed with `tomllib` after the 
edit, and `project.urls.Bluesky` reads 
`https://bsky.app/profile/airflow.apache.org` in each of them.
   
   closes: #76356
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (please specify the tool below)
   
   Generated-by: DeepSeek-V4.1-Flash (WorkBuddy) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   


-- 
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