ci(release): reject AppImage with bad sharun lib path#2385
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR extends the AppImage release pipeline by adding validation for sharun's Changessharun lib.path validation in AppImage stripping
Sequence DiagramsNo sequence diagram generated. The change is a single focused validation function addition without multi-component interactions. Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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.
Clean, well-targeted fix that prevents shipping broken AppImages. Addresses real user-reported launch failures on Fedora 43 (#2242) and Ubuntu 26.04 (#2368).
Changes
| File | Change |
|---|---|
scripts/release/strip-appimage-graphics-libs.sh |
New validate_sharun_lib_path() — fails release if shared/lib/lib.path is missing/empty or contains CI runner paths |
Notes
exit 1(vsreturn 1) is the right call here — a bad lib.path means the AppImage will fail on user machines, so aborting the entire release is correct.- Grep pattern properly handles PATH-separator-prefixed entries (
+and:). - Placement after
ensure_sharun_interpreteris logical — validate after ensuring the interpreter exists.
No issues found. LGTM — clean for approval.
graycyrus
left a comment
There was a problem hiding this comment.
Looks good, nice work!
Summary
Refs #2242
Refs #2368
Testing
Summary by CodeRabbit