Skip to content

Fix source link generation for providers#58367

Merged
potiuk merged 1 commit intoapache:mainfrom
potiuk:fix-source-packages-links-for-providers
Nov 16, 2025
Merged

Fix source link generation for providers#58367
potiuk merged 1 commit intoapache:mainfrom
potiuk:fix-source-packages-links-for-providers

Conversation

@potiuk
Copy link
Copy Markdown
Member

@potiuk potiuk commented Nov 16, 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

^ 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.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

@potiuk potiuk force-pushed the fix-source-packages-links-for-providers branch 3 times, most recently from 7e13187 to e9619cb Compare November 16, 2025 16:41
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
@potiuk potiuk force-pushed the fix-source-packages-links-for-providers branch from e9619cb to c2ad12b Compare November 16, 2025 17:21
@potiuk potiuk merged commit bbc1833 into apache:main Nov 16, 2025
118 checks passed
@potiuk potiuk deleted the fix-source-packages-links-for-providers branch November 16, 2025 18:21
@github-actions
Copy link
Copy Markdown

Backport failed to create: v3-1-test. View the failure log Run details

Status Branch Result
v3-1-test Commit Link

You can attempt to backport this manually by running:

cherry_picker bbc1833 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

@potiuk
Copy link
Copy Markdown
Member Author

potiuk commented Nov 16, 2025

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants