[bzawisto]

What changed

Runs CI against RedSuite 3.5.3. It accepts the -32001 cleaned-up block response, fixes a receipt discovery race, treats a dropped slow-subscriber connection as the client signal (#1876), and gives the retention scenarios enough time to observe ledger truncation on slow runners.

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The RedSuite CI action now checks out version 3.5.3 instead of 3.5.2.

Changes: RedSuite CI

Layer / File(s)	Summary
RedSuite checkout version .github/actions/run-redsuite/action.yml	The checkout ref changes from 3.5.2 to 3.5.3.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Possibly related PRs

• magicblock-labs/magicblock-validator#1836: This PR also pins RedSuite and adjusts its runner. It is part of the same RedSuite CI integration.
• magicblock-labs/magicblock-validator#1823: This PR introduced the Run RedSuite action and its pinned checkout, which this change updates.
• magicblock-labs/magicblock-validator#1865: This PR also updates the RedSuite revision used by the validator CI action.

Suggested labels: dependencies

Suggested reviewers: snawaz

Merge Risk: Minimal · up to 6db2f

No merge-blocking risk is established for the RedSuite version update; normal CI checks remain appropriate.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title "chore: bump redsuite to 3.5.3" matches the only file change, which updates the RedSuite checkout ref from 3.5.2 to 3.5.3 in the run-redsuite action. It is short, specific, and states the ma…
Description check		The description states that CI runs against RedSuite 3.5.3 and lists related behavior changes. It relates to the changeset, so it is on topic. It does not match the one-line diff exactly, but the chec…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title "chore: bump redsuite to 3.5.3" matches the only file change, which updates the RedSuite checkout ref from 3.5.2 to 3.5.3 in the run-redsuite action. It is short, specific, and states the main change.

Full details: Description check

Explanation

The description states that CI runs against RedSuite 3.5.3 and lists related behavior changes. It relates to the changeset, so it is on topic. It does not match the one-line diff exactly, but the check is lenient and the description is not off-topic.

Finishing Touches

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

• X
• Mastodon
• Reddit
• LinkedIn

Recent review info

Run configuration

• Source mode: Auto
• Repository: magicblock-labs/magicblock-validator
• Branch: master
• File: .coderabbit.yaml
• Commit: bcb9e41
• Layers: Repository YAML
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 7e44a547-e53d-4986-9ee1-77eb8e10643f

Commits

Reviewing files that changed from the base of the PR and between 37d4297 and 6db2ff7.

Files selected for processing: 1

• .github/actions/run-redsuite/action.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

[coderabbitai]

Additional comments: 1

.github/actions/run-redsuite/action.yml-36-36: 1

36-36: Minor · Potential issue · Low value

Unverified finding
We couldn't verify this from the code. It is shown for review, not as a verified issue.

The 3.5.0 checkout still uses a Yellowstone cache key based only on the Agave version and yellowstone.rs, unlike the RedSuite CLI and fixture caches keyed by checkout SHA. A plugin dependency changed elsewhere may therefore not invalidate the old cache.

CI may run with the 3.4.0 plugin, causing failures or results that do not reflect the intended 3.5.0 environment.

This can occur when: A 3.4.0 Yellowstone cache exists, and 3.5.0 changes a plugin build or selection input outside the two hashed files while those files remain unchanged.

Review info

Run configuration

• Source mode: Auto
• Repository: magicblock-labs/magicblock-validator
• Branch: master
• File: .coderabbit.yaml
• Commit: 5b52326
• Layers: Repository YAML
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 72a21278-4b50-4f9a-83c7-f7ba75a7b568

Commits

Reviewing files that changed from the base of the PR and between 5b52326 and ba98045.

Files selected for processing: 1

• .github/actions/run-redsuite/action.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.