removed old solc versions, use 0.8.x only instead

[gustavo-grieco]

Removed old solc versions tests, keeping only 0.8.x

Summary by CodeRabbit

• Chores
  • Updated the testing pipeline by replacing older Solidity compiler versions with newer releases.
  • Removed experimental configurations for legacy compiler versions, streamlining the overall testing setup.
  • Simplified and removed certain Solidity integration tests to reflect updated test coverage.

[coderabbitai]

Walkthrough

The CI configuration has been updated to modify the Solidity compiler versions used in the testing job. The outdated versions ("0.4.25", "0.5.7", "0.6.12", "0.7.5") have been removed and replaced with the versions "0.8.10" and "0.8.25". Additionally, the experimental configuration flags related to versions "0.6.12" and "0.7.5" have been removed, while the experimental configuration for "windows-latest" remains unchanged. In the test suites, certain Solidity contract tests targeting older compiler versions were removed, and one test case was simplified by removing explicit version and configuration parameters.

Changes

File	Change Summary
.github/workflows/ci.yml	Updated solc versions in the testing job: removed versions "0.4.25", "0.5.7", "0.6.12", "0.7.5"; added versions "0.8.10", "0.8.25"; removed experimental configs for 0.6.12 and 0.7.5 while keeping the Windows configuration intact.
src/test/Tests/Integration.hs	Removed tests for "basic/fallback.sol" (<0.6.0), "basic/gasuse.sol", and "basic/killed.sol" (<0.8.0) including their associated echidna test cases.
src/test/Tests/Research.hs	Simplified the test invocation for "research/harvey_baz.sol" by replacing testContract' with testContract, removing explicit version constraints and config parameters.

Poem

I'm a happy rabbit, racing through the CI,
New solc versions make my code dance and fly.
Out with the old, in with fresh, gleaming light,
Testing flows now hop with speed, day and night.
With every commit, my heart does a joyful sigh! 🐰✨

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 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 922884a and cf76f78.

📒 Files selected for processing (1)

• src/test/Tests/Integration.hs (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/test/Tests/Integration.hs

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

• GitHub Check: Build Echidna on windows-latest
• GitHub Check: Build Echidna on ubuntu-latest
• GitHub Check: Build Echidna on macos-13
• GitHub Check: Build macOS (x86_64) binary
• GitHub Check: Build macOS (aarch64) binary
• GitHub Check: Build Linux (x86_64) binary

---

🪧 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.
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/ci.yml (1)

208-211: Retention of the Windows Experimental Flag

The matrix’s include block still sets the experimental: true flag for windows-latest. As per the PR summary, experimental configurations for outdated solc versions were removed while keeping the Windows flag unchanged. Please confirm that retaining this experimental flag for the current 0.8.x tests is intentional and that it doesn’t cause any unintended behavior.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ec55378 and 05be755.

📒 Files selected for processing (1)

• .github/workflows/ci.yml (1 hunks)

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

• GitHub Check: Build Echidna on windows-latest
• GitHub Check: Build Echidna on ubuntu-latest
• GitHub Check: Build Echidna on macos-13
• GitHub Check: Build macOS (x86_64) binary
• GitHub Check: Build Linux (x86_64) binary
• GitHub Check: Build macOS (aarch64) binary

🔇 Additional comments (1)

.github/workflows/ci.yml (1)

206-207: Updated Solidity Compiler Versions

The test matrix now only includes Solidity compiler versions "0.8.10" and "0.8.25", which aligns perfectly with the PR objective to remove support for older solc versions. Please verify that any related scripts or configurations (e.g., those using solc-select) are fully compatible with these versions.