ci: fix upgrade smoke test broken since the 1.4.18 migration#119
Conversation
The smoke test asserted plugin_image_ratings_schema is present after the full migration chain, but migration 1.4.18 deliberately DELETEs the retired-plugin markers — the check failed on every run since 1.4.18 landed. Assert on search_fts_schema + plugin_analytics_pro_schema, which the chain actually leaves in place (mirrors the MigrationsTest fix).
|
Warning Review limit reached
Next review available in: 34 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
The upgrade smoke test asserts that
plugin_image_ratings_schemaexists after running the full migration chain, but migration 1.4.18 (already on main before PR #118) deliberately deletes the retired-plugin markers — so the workflow has failed on every run since. I switched the assertion tosearch_fts_schema+plugin_analytics_pro_schema, the markers the chain actually leaves in place, mirroring the MigrationsTest fix that shipped in #118.