Repository navigation
Bump the versioned branch links too when updating a release The second replace used old_version on both sides, so it did nothing and links like .../tensorflow/blob/r2.20/... kept pointing at the old release branch after running the script. - #2447
Open
rootkiller6788 wants to merge 1 commit into
Open
rootkiller6788 wants to merge 1 commit into
rootkiller6788 wants to merge 1 commit into
Conversation
The second replace used old_version on both sides, so it did nothing and links like .../tensorflow/blob/r2.20/... kept pointing at the old release branch after running the script.
PreviewPreview and run these notebook edits with Google Colab: Rendered notebook diffs available on ReviewNB.com.Format and styleUse the TensorFlow docs notebook tools to format for consistent source diffs and lint for style:$ python3 -m pip install -U --user git+https://github.com/tensorflow/docsIf commits are added to the pull request, synchronize your local branch: git pull origin fix-update-versions-branch-url
|
rootkiller6788
marked this pull request as ready for review
October 16, 2026 03:58
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.
Ran this script for a release update and noticed the branch links in the docs never move: the replace on these lines passes old_version on both sides, so it matches and writes back the same string. The version number itself goes up (that replace is above), but every link like
github.com/tensorflow/tensorflow/blob/r2.20/...stays on the old release branch.One character fix, use new_version on the right.
How I checked it: put a small md file with
2.20.0and ablob/r2.20/link in a temp dir, ran the script with--old_version 2.20.0 --new_version 2.21.0before and after the change. Before:Version 2.21.0 is current.but the link is stillblob/r2.20/. After:blob/r2.21/.