Skip to content

Update version.json #7023

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Oct 9, 2025
Merged

Update version.json #7023

merged 1 commit into from
Oct 9, 2025

Conversation

@buger
Copy link
Member

@buger buger commented Oct 9, 2025 •
edited by github-actions bot
Loading

User description

This pull request updates the version.json file

PR Type

Enhancement

Description

  • Promote docs to 5.10 Latest

  • Add branch mapping for release-5.10

  • Keep 5.9 as pinned archive

Diagram Walkthrough

flowchart LR
  v59["Docs 5.9"] -- "demote from Latest" --> v59arch["Archived 5.9 (/docs/5.9)"]
  latest["Latest Docs"] -- "promote" --> v510["5.10 (branch release-5.10)"]
Loading

File Walkthrough
Relevant files
Enhancement
versions.json
Promote 5.10 to Latest and archive 5.9                                     

scripts/versions.json

  • Set "5.10 - Latest" with branch release-5.10.
  • Added separate entry for 5.9 archived path.
  • Updated 5.9 name to "5.9" and kept branch.
 +6/-1     

@github-actions
Copy link
Contributor

github-actions bot commented Oct 9, 2025

⚠️ Deploy preview for PR #7023 did not become live after 3 attempts.
Please check Netlify or try manually: Preview URL

@github-actions
Copy link
Contributor

github-actions bot commented Oct 9, 2025

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review

Consistency Check

Ensure the "Latest" entry points to the correct branch and that routing/build tooling expects the first object to be the latest; verify no other files rely on "5.9 - Latest" naming.

 
    "path": "/docs/",
    "name": "5.10 - Latest",
    "branch": "release-5.10"
},
Path Validation

Confirm that the archived path "/docs/5.9/" matches existing hosting structure and that links/redirects are updated accordingly.

 
{
    "path": "/docs/5.9/",
    "name": "5.9",
    "branch": "release-5.9"

@github-actions
Copy link
Contributor

github-actions bot commented Oct 9, 2025

PR Code Suggestions ✨

Explore these optional code suggestions:

CategorySuggestion                                                                                                                                    Impact
Possible issue
Point latest to stable branch

Ensure the "Latest" entry points to a stable, published branch. If "release-5.10" is
not yet deployed, keep it on the stable branch to avoid broken links in production.

scripts/versions.json [3-6]

 {
     "path": "/docs/",
     "name": "5.10 - Latest",
-    "branch": "release-5.10"
+    "branch": "main"
 },
Suggestion importance[1-10]: 6

__

Why: The snippet matches lines 3-6 in the new hunk. The advice to ensure "Latest" maps to a stable deployed branch is reasonable but context-dependent; changing to main may be incorrect if release-5.10 is the intended deployed branch.

Low
General
Pin version to immutable tag

Keep versioned docs immutable by pinning "5.9" to the exact release tag or a frozen
branch. Using a moving "release-5.9" branch can drift and mismatch published docs.

scripts/versions.json [8-10]

 {
     "path": "/docs/5.9/",
     "name": "5.9",
-    "branch": "release-5.9"
+    "branch": "v5.9.0"
 },
Suggestion importance[1-10]: 5

__

Why: The snippet matches lines 8-10. Pinning to a tag can improve reproducibility, but it depends on project release workflow; suggesting v5.9.0 is speculative without confirming the tagging scheme.

Low

@sharadregoti sharadregoti merged commit 9a8499e into master Oct 9, 2025
13 checks passed
@sharadregoti sharadregoti deleted the update-version-json-18374540491 branch October 9, 2025 11:21
@sharadregoti
Copy link
Contributor

/release to release-5.9

@sharadregoti
Copy link
Contributor

/release to release-5.10

@tykbot
Copy link
Contributor

tykbot bot commented Oct 9, 2025

Working on it! Note that it can take a few minutes.

1 similar comment
@tykbot
Copy link
Contributor

tykbot bot commented Oct 9, 2025

Working on it! Note that it can take a few minutes.

tykbot bot pushed a commit that referenced this pull request Oct 9, 2025
@buger @sharadregoti
Update version.json (#7023)
26747ac 
[create-pull-request] automated change

Co-authored-by: sharadregoti <[email protected]>
(cherry picked from commit 9a8499e)
@buger buger mentioned this pull request Oct 9, 2025
Merged
@tykbot
Copy link
Contributor

tykbot bot commented Oct 9, 2025

@sharadregoti Seems like there is conflict and it require manual merge.

tykbot bot pushed a commit that referenced this pull request Oct 9, 2025
@buger @sharadregoti
Update version.json (#7023)
e4546c8 
[create-pull-request] automated change

Co-authored-by: sharadregoti <[email protected]>
(cherry picked from commit 9a8499e)
@buger buger mentioned this pull request Oct 9, 2025
Merged
@tykbot
Copy link
Contributor

tykbot bot commented Oct 9, 2025

@sharadregoti Seems like there is conflict and it require manual merge.

sharadregoti added a commit that referenced this pull request Oct 9, 2025
@buger @sharadregoti
Merging to release-5.10: Update version.json (#7023) (#7026)
c6d2484 
Update version.json (#7023)

[create-pull-request] automated change


(cherry picked from commit 9a8499e)

Co-authored-by: sharadregoti <[email protected]>
sharadregoti added a commit that referenced this pull request Oct 9, 2025
@buger @sharadregoti
Merging to release-5.9: Update version.json (#7023) (#7027)
a4289a3 
Update version.json (#7023)

[create-pull-request] automated change


(cherry picked from commit 9a8499e)

Co-authored-by: sharadregoti <[email protected]>
@sharadregoti
Copy link
Contributor

/release to release-5.3

@sharadregoti
Copy link
Contributor

/release to release-5.2

@sharadregoti
Copy link
Contributor

/release to release-5.1

@tykbot
Copy link
Contributor

tykbot bot commented Oct 9, 2025

Working on it! Note that it can take a few minutes.

2 similar comments
@tykbot
Copy link
Contributor

tykbot bot commented Oct 9, 2025

Working on it! Note that it can take a few minutes.

@tykbot
Copy link
Contributor

tykbot bot commented Oct 9, 2025

Working on it! Note that it can take a few minutes.

tykbot bot pushed a commit that referenced this pull request Oct 9, 2025
@buger @sharadregoti
Update version.json (#7023)
81989d8 
[create-pull-request] automated change

Co-authored-by: sharadregoti <[email protected]>
(cherry picked from commit 9a8499e)
@buger buger mentioned this pull request Oct 9, 2025
Closed
@tykbot
Copy link
Contributor

tykbot bot commented Oct 9, 2025

@sharadregoti Created merge PRs

@tykbot
Copy link
Contributor

tykbot bot commented Oct 9, 2025

Still working...

tykbot bot pushed a commit that referenced this pull request Oct 9, 2025
@buger @sharadregoti
Update version.json (#7023)
d6171ed 
[create-pull-request] automated change

Co-authored-by: sharadregoti <[email protected]>
(cherry picked from commit 9a8499e)
@buger buger mentioned this pull request Oct 9, 2025
Closed
@tykbot
Copy link
Contributor

tykbot bot commented Oct 9, 2025

@sharadregoti Created merge PRs

tykbot bot pushed a commit that referenced this pull request Oct 9, 2025
@buger @sharadregoti
Update version.json (#7023)
aaa510c 
[create-pull-request] automated change

Co-authored-by: sharadregoti <[email protected]>
(cherry picked from commit 9a8499e)
@buger buger mentioned this pull request Oct 9, 2025
Draft
@tykbot
Copy link
Contributor

tykbot bot commented Oct 9, 2025

@sharadregoti Created merge PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@sharadregoti sharadregoti sharadregoti approved these changes

Assignees

@sharadregoti sharadregoti

Labels

major-release-gh release-5.9 release-5.10 Review effort 1/5

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@buger @sharadregoti