fix: e2e-evm-cron.yml

[Unique-Divine]

Purpose / Abstract

• Continues from chore: scheduled basic e2e tests for evm testnet endpoint #2106 to get the GitHub workflow running successfully

Summary by CodeRabbit

• New Features

  • Added a new installation step for the just command-line tool in E2E tests.
  • Enabled WASM light clients on IBC.
  • Introduced features for fun token creation fee validation and gas usage limits.

• Bug Fixes

  • Improved state consistency during precompile execution and ERC20 transfers.

• Documentation

  • Updated CHANGELOG.md to reflect changes from a recent audit, detailing new features, bug fixes, and refactorings.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces modifications to the EVM end-to-end (E2E) test workflow and updates the CHANGELOG.md file. In the workflow, a new step for installing the just command-line tool is added, and two environment variables, MNEMONIC and SLACK_WEBHOOK_URL, are updated to reference different secrets. The CHANGELOG.md reflects changes made post-audit, detailing new features, bug fixes, and refactorings in the Nibiru EVM codebase, ensuring comprehensive documentation of the recent updates.

Changes

File	Change Summary
.github/workflows/e2e-evm-cron.yml	- Added step to install just command-line tool. - Updated MNEMONIC from WALLET_MNEMONIC_TESTNET to MNEMONIC_TESTNET1_VALIDATOR. - Updated SLACK_WEBHOOK_URL from SLACK_WEBHOOK_TESTNET to SLACK_WEBHOOK_URL.
CHANGELOG.md	- Updated with entries for changes made post-audit (Oct 7, 2024 - Nov 1, 2024). - Added features, bug fixes, and refactorings including debug_traceCall, eth_getTransactionReceipt, and methods in evm-funtoken-precompile.

Possibly related PRs

• chore: scheduled basic e2e tests for evm testnet endpoint #2106: The changes in the main PR regarding the EVM end-to-end tests workflow are related to the new scheduled basic E2E tests workflow introduced in this PR, as both involve modifications to GitHub Actions workflows for EVM testing.

Suggested reviewers

• Unique-Divine

Poem

🐰 In the land of code where rabbits play,
New tools are added to brighten the day.
Secrets updated, workflows refined,
In the world of EVM, progress aligned.
With every change, we hop and cheer,
For a future of coding that's bright and clear! 🌟

---

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 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.