Fix WhatsApp version check in maintained apps ingestion#48504
Fix WhatsApp version check in maintained apps ingestion#48504sharon-fdm wants to merge 2 commits into
Conversation
WhatsApp changed their version scheme from "2.x.y.z" to "26.x.y". The version shortener was erroring on versions without the legacy "2." prefix, causing the entire maintained apps ingestion to panic. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #48504 +/- ##
==========================================
+ Coverage 67.32% 67.84% +0.51%
==========================================
Files 3657 3667 +10
Lines 231264 233255 +1991
Branches 12206 12206
==========================================
+ Hits 155694 158246 +2552
+ Misses 61601 60745 -856
- Partials 13969 14264 +295
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
CI Feedback 🧐A test triggered by this PR failed. Here is an AI-generated analysis of the failure:
|
Summary
2.x.y.zto26.x.yWhatsAppVersionShortenerwas erroring on versions without the legacy2.prefix, causing the maintained apps ingestion workflow to panic and fail on main2.prefix instead of erroringChecklist for submitter
changes/,orbit/changes/oree/fleetd-chrome/changes.SELECT *is avoided, SQL injection is prevented (using placeholders for values in statements), JS inline code is prevented especially for url redirects, and untrusted data interpolated into shell scripts/commands is validated against shell metacharacters.Testing
🤖 Generated with Claude Code