Use "top" version when preparing provider packages #13271
Comments
9 tasks
potiuk
modified the milestones:
Airflow 2.0 clean-up,
apache-airflow-providers-google v2
potiuk
added a commit
to higrys/airflow
that referenced
this issue
Jan 24, 2021
This change implements per-provider versioning tools. Version of the providers is retrieved from provider.yaml file (top-level verion). Documentation is generated in the documentation folder rather than in sources and embedded in provider's index. Backport providers remain as they were until we delete all the backport references in April 2021 nd then the code can be simplified and the backport functionality can be removed then. When generating multiple providers, only those that have version that has no corresponding `providers-<PROVIDER>/<VERSION>` are generated. Other providers are skipped with warnings. Fixes: apache#13272, apache#13271, apache#13274, apache#13276, apache#13277, apache#13275, apache#13273
potiuk
added a commit
to PolideaInternal/airflow
that referenced
this issue
Feb 1, 2021
This change implements per-provider versioning tools. Version of the providers is retrieved from provider.yaml file (top-level verion). Documentation is generated in the documentation folder rather than in sources and embedded in provider's index. Backport providers remain as they were until we delete all the backport references in April 2021 nd then the code can be simplified and the backport functionality can be removed then. When generating multiple providers, only those that have version that has no corresponding `providers-<PROVIDER>/<VERSION>` are generated. Other providers are skipped with warnings. Old documentation is removed and new CHANGELOG.rst have been prepared for all providers to accomodate to the new process (which is comming as a follow-up commit) Fixes: apache#13272, apache#13271, apache#13274, apache#13276, apache#13277, apache#13275, apache#13273
potiuk
added a commit
that referenced
this issue
Feb 1, 2021
This change implements per-provider versioning tools. Version of the providers is retrieved from provider.yaml file (top-level verion). Documentation is generated in the documentation folder rather than in sources and embedded in provider's index. Backport providers remain as they were until we delete all the backport references in April 2021 nd then the code can be simplified and the backport functionality can be removed then. When generating multiple providers, only those that have version that has no corresponding `providers-<PROVIDER>/<VERSION>` are generated. Other providers are skipped with warnings. Old documentation is removed and new CHANGELOG.rst have been prepared for all providers to accomodate to the new process (which is comming as a follow-up commit) Fixes: #13272, #13271, #13274, #13276, #13277, #13275, #13273
potiuk
added a commit
that referenced
this issue
Mar 3, 2021
This change implements per-provider versioning tools. Version of the providers is retrieved from provider.yaml file (top-level verion). Documentation is generated in the documentation folder rather than in sources and embedded in provider's index. Backport providers remain as they were until we delete all the backport references in April 2021 nd then the code can be simplified and the backport functionality can be removed then. When generating multiple providers, only those that have version that has no corresponding `providers-<PROVIDER>/<VERSION>` are generated. Other providers are skipped with warnings. Old documentation is removed and new CHANGELOG.rst have been prepared for all providers to accomodate to the new process (which is comming as a follow-up commit) Fixes: #13272, #13271, #13274, #13276, #13277, #13275, #13273 (cherry picked from commit ac2f72c)
potiuk
added a commit
that referenced
this issue
Mar 3, 2021
This change implements per-provider versioning tools. Version of the providers is retrieved from provider.yaml file (top-level verion). Documentation is generated in the documentation folder rather than in sources and embedded in provider's index. Backport providers remain as they were until we delete all the backport references in April 2021 nd then the code can be simplified and the backport functionality can be removed then. When generating multiple providers, only those that have version that has no corresponding `providers-<PROVIDER>/<VERSION>` are generated. Other providers are skipped with warnings. Old documentation is removed and new CHANGELOG.rst have been prepared for all providers to accomodate to the new process (which is comming as a follow-up commit) Fixes: #13272, #13271, #13274, #13276, #13277, #13275, #13273 (cherry picked from commit ac2f72c)
potiuk
added a commit
that referenced
this issue
Mar 3, 2021
This change implements per-provider versioning tools. Version of the providers is retrieved from provider.yaml file (top-level verion). Documentation is generated in the documentation folder rather than in sources and embedded in provider's index. Backport providers remain as they were until we delete all the backport references in April 2021 nd then the code can be simplified and the backport functionality can be removed then. When generating multiple providers, only those that have version that has no corresponding `providers-<PROVIDER>/<VERSION>` are generated. Other providers are skipped with warnings. Old documentation is removed and new CHANGELOG.rst have been prepared for all providers to accomodate to the new process (which is comming as a follow-up commit) Fixes: #13272, #13271, #13274, #13276, #13277, #13275, #13273 (cherry picked from commit ac2f72c)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should use the first version from the list of versions in provider.yaml as version of the package to build.
The text was updated successfully, but these errors were encountered: