Repository navigation
Release v1.13.2 - #3613
Release v1.13.2#3613
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (81)
📝 WalkthroughWalkthroughVersion bump from 1.13.1 to 1.13.2 across the entire Sherpa ONNX project: CMake and C++ build metadata, changelog, Android/iOS/macOS app versions, Flutter plugins and examples, Dart examples, HarmonyOS packages, Rust crates, Python wheels, Node.js packages, Maven projects, and all supporting documentation. ChangesVersion Bump 1.13.1 to 1.13.2
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Code Review
This pull request updates the project version from 1.13.1 to 1.13.2 across all relevant configuration files, including Android, iOS, HarmonyOS, Rust, Python, Dart, and Flutter, and updates the internal version metadata. A review comment suggests simplifying the new_version variable in new-release.sh by removing unnecessary backslashes to ensure better portability in sed commands.
| old_version="1\.13\.0" | ||
| new_version="1\.13\.1" | ||
| old_version="1\.13\.1" | ||
| new_version="1\.13\.2" |
There was a problem hiding this comment.
The new_version variable is used as the replacement string in several sed commands throughout this script. In the replacement part of a sed substitution (s/find/replace/), backslashes are typically used to escape special characters like &, \, or the delimiter itself. Including backslashes to escape dots (e.g., 1\.13\.2) is unnecessary and non-portable; while some sed implementations might strip them, others may treat them literally, which could result in literal backslashes being inserted into the version strings of your configuration files. It is safer to use the literal version string for the replacement.
| new_version="1\.13\.2" | |
| new_version="1.13.2" |
Summary by CodeRabbit