fix: improve legacy version detection for translation service #207
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
Unit Test Results10 tests 10 ✅ 1s ⏱️ Results for commit 8e843ac. ♻️ This comment has been updated with latest results. |
TheMeinerLP
deleted the
themeinerlp/hotfix/GH-206_fix_dection_for_legacy_translation
branch
github-actions bot
pushed a commit
that referenced
this pull request
Nov 21, 2025
## [2.7.2](v2.7.1...v2.7.2) (2025-11-21) ### Bug Fixes * improve legacy version detection for translation service ([2108329](2108329)) * improve legacy version detection for translation service ([#207](#207)) ([ae1396c](ae1396c)) * suppress deprecation warning in translation service provider ([8e843ac](8e843ac))
|
🎉 This PR is included in version 2.7.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Proposed changes
Add semversion parser into translation service to correctly handle versions like "1.21.3" to improve legacy translation detection as a result.
This pr fixes #206.
Types of changes
What types of changes does your code introduce to this project?
Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any ofthem, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you
did and what alternatives you considered, etc...