[BACKPORT] Complete automation of version replacement pre-commit for pip and uv … #43623
Conversation
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
…pache#43205) The scripts to update pip and uv version were not complete - they did not replace a few of our scripts and documentation. This was especially troublesome for doc replacement, because updating versions manually led to misalignments of tables in markdown. Lack of completeness of the upgrade caused apache#43197 and apache#43135 manual PRs to bump all references. Also an earlier upgrade caused the markdown table to be broken - with UV row table offset by 1. This PR fixes it: * all the scripts and docs are updated now * when markdown is updated, the table structure is not broken (cherry picked from commit 7ede73c)
potiuk
changed the title
Member
Author
|
Backport of #43205 |
Member
Author
|
Backporting some recent changes - to enable switching to uv for v2-10-test/stable in ordert to speed up next 2.10.* preparation and switching between branches (mostly to help @utkarsharma2 and @ephraimbuddy and anyone who cherry-picks bugfixes) |
gopidesupavan
approved these changes
Nov 4, 2024
amoghrajesh
approved these changes
Nov 4, 2024
Member
Author
|
Just random node issue :) |
utkarsharma2
pushed a commit
that referenced
this pull request
Dec 4, 2024
…43205) (#43623) The scripts to update pip and uv version were not complete - they did not replace a few of our scripts and documentation. This was especially troublesome for doc replacement, because updating versions manually led to misalignments of tables in markdown. Lack of completeness of the upgrade caused #43197 and #43135 manual PRs to bump all references. Also an earlier upgrade caused the markdown table to be broken - with UV row table offset by 1. This PR fixes it: * all the scripts and docs are updated now * when markdown is updated, the table structure is not broken (cherry picked from commit 7ede73c)
33 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
…(#43205)
The scripts to update pip and uv version were not complete - they did not replace a few of our scripts and documentation. This was especially troublesome for doc replacement, because updating versions manually led to misalignments of tables in markdown.
Lack of completeness of the upgrade caused #43197 and #43135 manual PRs to bump all references.
Also an earlier upgrade caused the markdown table to be broken - with UV row table offset by 1.
This PR fixes it:
(cherry picked from commit 7ede73c)
^ 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 newsfragments.