Increase SignatureChecker minimum pragma to 0.8.24

[ernestognw]

Fixes #????

PR Checklist

• Tests
• Documentation
• Changeset entry (run npx changeset add)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 45704d4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Amxx]

My understanding is:

• SignatureChecker doesn't need 0.8.24 now
• SignatureChecker will need 0.8.24 when the ERC-7913 validation gets added
• This PR is done ahead of the ERC-7913 addition to avoid the ERC-7913 PR touching too many files?

If this is all correct, then I approve.

more discussion

[Amxx]

I'm really wondering how much of a breaking change it is. I know @ernestognw wants to move forward with small things like that. I also don't think its a major issue at all ... but it might technically break projects that use Governor (or just SignatureChecker) and have pinned a version of the compiler >=0.8.20, <0.8.24.

Maybe we want to add a "breaking change" entry to the Changelog saying that some contract compiler requirement have evolved, and that users may need to upgrade the compiler version they are using.

[ernestognw]

My understanding is:

• SignatureChecker doesn't need 0.8.24 now
• SignatureChecker will need 0.8.24 when the ERC-7913 validation gets added
• This PR is done ahead of the ERC-7913 addition to avoid the ERC-7913 PR touching too many files?

If this is all correct, then I approve.

Yes, this is correct. Basically moving 7913Utils to SIgnatureChecker forced this pragma increase.

Maybe we want to add a "breaking change" entry to the Changelog saying that some contract compiler requirement have evolved, and that users may need to upgrade the compiler version they are using.

Also true, I added a small note I think should be good enough