Update forge and change visibility in fuzz tests #5103
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
|
Amxx
previously approved these changes
Jul 3, 2024
cairoeth
approved these changes
Oct 27, 2024
Amxx
approved these changes
Oct 28, 2024
Amxx
pushed a commit
to Amxx/openzeppelin-contracts
that referenced
this pull request
Nov 30, 2024
Co-authored-by: cairo <cairoeth@protonmail.com> Signed-off-by: Hadrien Croubois <hadrien.croubois@gmail.com>
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.
Fixes #????
After upgrading forge some fuzz tests now compile with a warning suggesting to change visibility. We didn't care about this before but it'd be nice to silence compile warnings for those using forge with the library installed.
PR Checklist
npx changeset add)