Repository navigation
revert: defer dlp v2 coverage until validator support - #296
Merged
Merged
Conversation
This was referenced Nov 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Remove the DLP v2 settlement coverage merged in #284, #285, and #287. Those scenarios require validator support that is still under development in magicblock-labs/magicblock-validator#1860 and a DLP change in magicblock-labs/delegation-program#271. Keeping them on
mainwould make the suite appear ready to qualify v2 settlement before that path works.This revert restores the tree from immediately before the three PRs. Their merged commits remain available to reapply when the validator and DLP are ready. Coverage issues #281, #282, and #283 will be reopened after this revert merges.
Impact
The three v2 scenario names and
REDSUITE_DLP_SOoverride are removed frommainuntil the matching validator can run them. Existing default Redshift runs retain their pre-stack behavior.