Chaiweb 3 2 release - #31
Merged
Merged
Conversation
kdafriend
force-pushed
the
chaiweb_3_2_release
branch
from
July 31, 2026 08:13
d60af05 to
b5750fa
Compare
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
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.
This PR prepares the chainweb release..
Some notes:
The mess in imports in some files come from the fact that I reorganized months ago export of the Pact package. Making a lot of imports redundant.
The validations tests had to slighty modified. Because the test suite considered that evry ForkNumber different from 0 was Unknown. This is not true anymore. I assumed that in most tests, catching the UnknownForkNumber was ""accidental"" And I assumed that catching UnknownForkNumber was only desired in tests 12 and 13