Skip to content

ci: fix upgrade smoke test broken since the 1.4.18 migration#119

Merged
fabiodalez-dev merged 1 commit into
mainfrom
fix/upgrade-smoke-retired-markers
Jul 8, 2026
Merged

ci: fix upgrade smoke test broken since the 1.4.18 migration#119
fabiodalez-dev merged 1 commit into
mainfrom
fix/upgrade-smoke-retired-markers

Conversation

@fabiodalez-dev

Copy link
Copy Markdown
Owner

The upgrade smoke test asserts that plugin_image_ratings_schema exists 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 to search_fts_schema + plugin_analytics_pro_schema, the markers the chain actually leaves in place, mirroring the MigrationsTest fix that shipped in #118.

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).
@coderabbitai

coderabbitai Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@fabiodalez-dev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 34 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3fcdaabd-d985-4771-b5b4-b1a6cad8d11e

📥 Commits

Reviewing files that changed from the base of the PR and between fa84807 and 14ece4b.

📒 Files selected for processing (1)
  • .github/workflows/upgrade-smoke.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/upgrade-smoke-retired-markers

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@fabiodalez-dev
fabiodalez-dev merged commit e0372d1 into main Jul 8, 2026
3 of 4 checks passed
@fabiodalez-dev
fabiodalez-dev deleted the fix/upgrade-smoke-retired-markers branch July 8, 2026 11:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant