chore: bump versioned constants to 0.13.1 #743
Merged
Conversation
This file contains 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
tcoratger
previously approved these changes
Sep 6, 2024
greged93
previously approved these changes
Sep 6, 2024
tcoratger
approved these changes
Sep 6, 2024
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.
Pull Request type
Time spent on this PR:
Resolves: #{Issue number}
Please check the type of change your PR introduces:
What is the new behavior?
Updates the
versioned_constants.jsonfiles to 0.13.1.1. This file describes the pricing of different operations performed, and is used during fee computation.The issue we had was that blockifier accepted usage of the range_check96 and add_mod builtins, but our sequencer crate was providing a block context without pricing for these variables.
Does this introduce a breaking change?