Update solc and evm version

[0xDEnYO]

Which Jira task belongs to this PR?

Why did I implement it this way?

We used to have typescript and other compatibility issues when running our codebase on higher solidity version but that seems to have changed now. Our auditor (Sujith) has confirmed that changing to newer solc and evm version does not impose a security risk.

Checklist before requesting a review

• I have performed a self-review of my code
• This pull request is as small as possible and only tackles one problem
• I have added tests that cover the functionality / test the bug
• For new facets: I have checked all points from this list: https://www.notion.so/lifi/New-Facet-Contract-Checklist-157f0ff14ac78095a2b8f999d655622e
• I have updated any required documentation

Checklist for reviewer (DO NOT DEPLOY and contracts BEFORE CHECKING THIS!!!)

• I have checked that any arbitrary calls to external contracts are validated and or restricted
• I have checked that any privileged calls (i.e. storage modifications) are validated and or restricted
• I have ensured that any new contracts have had AT A MINIMUM 1 preliminary audit conducted on by <company/auditor>

[coderabbitai]

Walkthrough

The changes update the Solidity compiler and EVM versions in the main configuration (foundry.toml), shifting from version 0.8.17 to 0.8.22 and from “shanghai” to “cancun” respectively. In addition, multiple test files have been modified to change the Solidity pragma declaration from a fixed version ("0.8.17") to a caret requirement ("^0.8.17"), broadening compatibility. No modifications were made to the public or exported entities in any file.

Changes

File(s)	Change Summary
foundry.toml	Updated Solidity compiler version from 0.8.17 to 0.8.22 and EVM version from "shanghai" to "cancun".
test/solidity/.../*.t.sol (Facets, Helpers, Periphery)	Changed Solidity pragma directive from pragma solidity 0.8.17; to pragma solidity ^0.8.17; in all test files.

Possibly related PRs

• Small codebase fixes #946 – Addresses Solidity compiler version updates similar to this PR with direct code-level modifications.
• deploy relay facet to gravity chain #961 – Involves adjustments in foundry.toml and test files’ Solidity pragma declarations, closely matching the changes here.
• Audit fixes [GasZipFacet v2.0.2] #910 – Specifically updates Solidity versions in Permit2Proxy, aligning with the versioning changes in this PR.

Suggested labels

AuditCompleted, AuditRequired

Suggested reviewers

• ezynda3
• mirooon

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)

• JIRA integration encountered authorization issues. Please disconnect and reconnect the integration in the CodeRabbit UI.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2cc7956 and cb1c6c6.

📒 Files selected for processing (6)

• foundry.toml (1 hunks)
• test/solidity/Facets/GasZipFacet.t.sol (1 hunks)
• test/solidity/Facets/RelayFacet.t.sol (1 hunks)
• test/solidity/Helpers/WithdrawablePeriphery.t.sol (1 hunks)
• test/solidity/Periphery/GasZipPeriphery.t.sol (1 hunks)
• test/solidity/Periphery/Permit2Proxy.t.sol (1 hunks)

✅ Files skipped from review due to trivial changes (5)

• test/solidity/Facets/RelayFacet.t.sol
• test/solidity/Periphery/Permit2Proxy.t.sol
• test/solidity/Periphery/GasZipPeriphery.t.sol
• test/solidity/Facets/GasZipFacet.t.sol
• test/solidity/Helpers/WithdrawablePeriphery.t.sol

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: run-unit-tests
• GitHub Check: enforce-min-test-coverage
• GitHub Check: run-unit-tests
• GitHub Check: enforce-min-test-coverage

🔇 Additional comments (2)

foundry.toml (2)

3-3: Update Solidity Compiler Version
The 'solc_version' has been successfully updated to '0.8.22'. This change aligns with the PR objectives and should provide access to the latest compiler features and optimizations. Please verify that all contracts compile without warnings and that any potential changes in behavior (due to compiler updates) are addressed in your tests or documentation.

---

4-4: Update EVM Version
The 'evm_version' is now set to 'cancun', which meets the updated requirements. Ensure that this change has been thoroughly verified with your test suite and that any tooling integrated with the EVM (e.g., simulators or deployment scripts) is compatible with the new version.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.