-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't export coerceKeyRole, export RewardAccount #708
Don't export coerceKeyRole, export RewardAccount #708
Conversation
f0165bd
to
3590176
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but it does seem breaking. It would need to be noted in the changelog
@Jimbo4350> confirmed with lehins that the only valid use of coercing key roles is for the
|
There was a 10.4.0.0 release between #699 and #708 therefore this is a breaking change.
|
Changelog
Context
coerceKeyRole
is no longer necessary for solving [FEATURE] - Updatecardano-cli conway query spo-stake-distribution
cardano-cli#911, which is good; because @Jimbo4350 had concerned about it (on Slack). I must say I readied Export HasKeyRole's coerceKeyRole function #699 too fast.Not marking this one as breaking, because it actually reverts #699. Since there was no release since 699, overall it's not going to be a breaking change.Edit: There was 10.4.0.0 release, so marking it as breaking
How to trust this PR
The new export only concerns a data structure, nothing controversial
Checklist