This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch v3-0-test
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/v3-0-test by this push:
     new 631d0d335c4 [v3-0-test] Fix broken link in contributors doc on 
providers (#53344) (#53347)
631d0d335c4 is described below

commit 631d0d335c49bb437a164f12441c9b3ffcb33227
Author: github-actions[bot] 
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Mon Jul 14 22:05:11 2025 +0200

    [v3-0-test] Fix broken link in contributors doc on providers (#53344) 
(#53347)
    
    (cherry picked from commit a6efa53040c43dbf2903cb667116ed162916e041)
    
    Co-authored-by: Zach <[email protected]>
---
 contributing-docs/12_provider_distributions.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/contributing-docs/12_provider_distributions.rst 
b/contributing-docs/12_provider_distributions.rst
index bf14b56aca0..f85f1daa4ba 100644
--- a/contributing-docs/12_provider_distributions.rst
+++ b/contributing-docs/12_provider_distributions.rst
@@ -169,7 +169,7 @@ there where you should add and remove dependencies for 
providers (following by r
 of Airflow).
 
 The ``provider.yaml`` file is compliant with the schema that is available in
-`json-schema specification 
<https://github.com/apache/airflow/blob/main/airflow/provider.yaml.schema.json>`_.
+`json-schema specification 
<https://github.com/apache/airflow/blob/main/airflow-core/src/airflow/provider.yaml.schema.json>`_.
 
 Thanks to that mechanism, you can develop community managed providers in a 
seamless way directly from
 Airflow sources, without preparing and releasing them as distributions 
separately, which would be rather

Reply via email to