NFData instance for MockKES #623
Merged
+8
−1
Conversation
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
coot
force-pushed
the
coot/nfdata-for-mock-kes-2.2.3.2
branch
from
58d594b to
bf838b5
Compare
lehins
approved these changes
Feb 9, 2026
lehins
requested changes
Feb 9, 2026
lehins
approved these changes
Feb 9, 2026
Collaborator
lehins
left a comment
lehins
left a comment
There was a problem hiding this comment.
Actually nevermind. We'll just need to add a changelog entry to cardano-crypto-class-2.3.0.0 mentioning removal of this NFData instance, and then again addition in cardano-crypto-class-2.3.1.0
lehins
merged commit e2ecd36
into
release/cardano-crypto-class-2.2.3.2
22 of 32 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
NFDatainstance forMocKEScardano-crypto-classto2.2.4.0There's also a related PR to
masterbranch: #624.Checklist
CHANGELOG.mdfor the affected packages.New section is never added with the code changes. (See RELEASING.md)
.cabalandCHANGELOG.mdfiles according to theversioning process.
.cabalfiles for all affected packages are updated.If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)