psysonic: Update to version 1.51.0, fix checkver - #18542
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan includes up to 8 reviews per rolling hour; 7 remain after this review. 📝 WalkthroughWalkthroughUpdated Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to The PR makes a localized manifest and release-detection update, and no actionable merge-blocking risk remains after normal maintainer checks. Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 |
|
/verify |
|
Your changes did not pass all checks. Please address the issues in the manifest and comment starting with psysonic
|
GitHub mode now sets jsonpath '$.tag_name' when a token is present, so the regex matches against the tag name instead of the releases page. 'app-v([\d.]+)' works in both the API and the HTML path.
|
/verify The regex was written against the releases page, but GitHub mode sets |
|
All changes look good. Wait for review from human collaborators. psysonic
|
The upstream repository moved from
Psychotoxical/psysonictoPsysonic/psysonic(organization transfer). All URLs updated; the old ones still redirect, so nothing was broken.Also fixes autoupdate, which is why this manifest sat at 1.50.0:
checkverscraped the repository landing page forPsysonic v([\d.]+), and that string is no longer present in its HTML. It now reads/releases/latestand matches the project'sapp-vtag prefix, which also keeps release candidates out.Checksum is GitHub's own digest for the published installer.