Fix source link generation for providers#58367
Merged
potiuk merged 1 commit intoapache:mainfrom Nov 16, 2025
Merged
Conversation
jscheffl
reviewed
Nov 16, 2025
jscheffl
approved these changes
Nov 16, 2025
7e13187 to
e9619cb
Compare
After adding -source package with release date to providers release, we also need to update the source download documentation to link to the right source tarball. This PR adds the last missing bits and pieces to do that: 1) Updates information about format of RELEASE_DATE and supported (potentially) YYYY_MM_DD_NN format 2) The release date parameter is used and verified at release docuemntation preparation time and it's stored in "providers/.last_release_date.txt" 3) The relase date of the current release (stored in the commit which is used to release providers) is used to produce the right links - both in "providers summary" and in individual provider's package documntation
e9619cb to
c2ad12b
Compare
Backport failed to create: v3-1-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker bbc1833 v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
Member
Author
|
No need to backport. |
aaron-wolmutt
pushed a commit
to aaron-wolmutt/airflow
that referenced
this pull request
Nov 20, 2025
After adding -source package with release date to providers release, we also need to update the source download documentation to link to the right source tarball. This PR adds the last missing bits and pieces to do that: 1) Updates information about format of RELEASE_DATE and supported (potentially) YYYY_MM_DD_NN format 2) The release date parameter is used and verified at release docuemntation preparation time and it's stored in "providers/.last_release_date.txt" 3) The relase date of the current release (stored in the commit which is used to release providers) is used to produce the right links - both in "providers summary" and in individual provider's package documntation
Copilot AI
pushed a commit
to jason810496/airflow
that referenced
this pull request
Dec 5, 2025
After adding -source package with release date to providers release, we also need to update the source download documentation to link to the right source tarball. This PR adds the last missing bits and pieces to do that: 1) Updates information about format of RELEASE_DATE and supported (potentially) YYYY_MM_DD_NN format 2) The release date parameter is used and verified at release docuemntation preparation time and it's stored in "providers/.last_release_date.txt" 3) The relase date of the current release (stored in the commit which is used to release providers) is used to produce the right links - both in "providers summary" and in individual provider's package documntation
itayweb
pushed a commit
to itayweb/airflow
that referenced
this pull request
Dec 6, 2025
After adding -source package with release date to providers release, we also need to update the source download documentation to link to the right source tarball. This PR adds the last missing bits and pieces to do that: 1) Updates information about format of RELEASE_DATE and supported (potentially) YYYY_MM_DD_NN format 2) The release date parameter is used and verified at release docuemntation preparation time and it's stored in "providers/.last_release_date.txt" 3) The relase date of the current release (stored in the commit which is used to release providers) is used to produce the right links - both in "providers summary" and in individual provider's package documntation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After adding -source package with release date to providers release, we also need to update the source download documentation to link to the right source tarball.
This PR adds the last missing bits and pieces to do that:
(potentially) YYYY_MM_DD_NN format
docuemntation preparation time and it's stored in
"providers/.last_release_date.txt"
which is used to release providers) is used to produce the
right links - both in "providers summary" and in individual
provider's package documntation
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.