bump client versions and fix update-config-versions.js sorting#454
Merged
Conversation
![orca-security-eu[bot]](https://avatars.githubusercontent.com/in/276244?s=60&v=4){kind=small}
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
 Passed |
Infrastructure as Code |  0  0  0  0 |
View in Orca |
| Passed |
SAST | 0 0 0 0 |
View in Orca |
| Passed |
Secrets | 0 0 0 0 |
View in Orca |
| Passed |
Vulnerabilities | 0 0 0 0 |
View in Orca |
Contributor
There was a problem hiding this comment.
⚠️ Not ready to approve
The updated tag-stripping logic uses replace('v',''), which does not reliably remove only a leading v prefix and can corrupt non-standard tag names.
Pull request overview
Updates the docs site’s dynamic client-version configuration so automated builds select the true latest GitHub release versions (especially once minor/patch versions reach double digits), and refreshes the local fallback versions used for local builds.
Changes:
- Fixes
_build_scripts/update-config-versions.jsto use numeric-aware sorting when selecting the highest release tag. - Bumps several fallback client/tool versions in
versions-config.json(TypeScript, Python, Helm, CLI, Agents SDKs, C#).
File summaries
| File | Description |
|---|---|
| versions-config.json | Updates local fallback version pins for multiple clients/tools. |
| _build_scripts/update-config-versions.js | Adjusts release tag processing/sorting to avoid lexicographic “latest” selection errors. |
Copilot's findings
- Files reviewed: 2/2 changed files
- Comments generated: 2
Note
Your feedback helps us improve the quality of this feature.
Please use 👍 or 👎 to tell us whether this assessment is correct.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| .replace('v', '') // remove the v from the name "v1.26.1" => "1.26.1" | ||
| .filter(item => !item.prerelease) // remove pre-release items | ||
| .filter(item => !item.draft) // remove draft releases | ||
| .map(item => item.tag_name.replace('v', '')) // strip the v: "v1.26.1" => "1.26.1" |
Comment on lines
+45
to
+46
| .sort((a, b) => // semver-aware sort – ascending | ||
| a.localeCompare(b, undefined, { numeric: true, sensitivity: 'base' })) |
g-despot
approved these changes
Jun 18, 2026
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.
What's being changed:
Bug: The version-fetching script (_build_scripts/update-config-versions.js) sorted release tags with JavaScript's default lexicographic .sort(), so v3.9.0 ranked above v3.13.1 ('9' > '1' character-wise). It picked the wrong "latest," which is why the TypeScript client-libraries page showed an outdated version. The automation was running fine — it was just choosing wrong.
Fix:
Tested: Ran the script live (exit 0, all clients resolved correctly).
Status: Both changes staged on branch bump-client-versions-and-fix-sorting, not committed.
Note: Affects all clients, not just TS — any client crossing into double-digit minor/patch would've hit the same bug.
Type of change:
How has this been tested?
Yes, locally and with claude ;)
yarn start