chore: Update package.json order, and touch files for CI

[CryptoFewka]

This PR will:

• Update dependencies to be above devDependencies in package.json
• Touch previously altered files to ensure the CI picks them up as changes.

Summary by CodeRabbit

• Chores
  • Removed the chokidar dependency from project configurations.
• New Features
  • Enhanced Hardhat configuration to support additional blockchain networks and multiple Solidity compiler versions, improving the development environment.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

📝 Walkthrough

Walkthrough

The changes in this pull request involve modifications to the package.json file for the @zetachain/protocol-contracts project, where the dependency chokidar has been removed entirely. Additionally, the hardhat.config.ts file has been enhanced to include API keys for multiple networks, expanded custom chain configurations, and support for various Solidity compiler versions.

Changes

File	Change Summary
v1/package.json	Removed dependency: "chokidar": "^4.0.1"; dependencies section cleared.
v1/hardhat.config.ts	Enhanced Hardhat configuration with new API keys for amoy_testnet, base_mainnet, and base_testnet; added custom chains; defined multiple Solidity compiler versions.

Possibly related PRs

• chore: add data for Base mainnet go live (part one) #372: This PR modifies the v1/hardhat.config.ts file to add a custom chain configuration for base_mainnet, which is directly related to the changes made in the main PR regarding the Hardhat configuration.
• chore: Add base mainnet addresses for go live #373: This PR also updates the v1/hardhat.config.ts file to include a new custom chain configuration for base_mainnet, indicating a direct connection to the main PR's changes in the Hardhat configuration.

---

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.

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

🧹 Outside diff range and nitpick comments (1)

v1/package.json (1)

95-95: Consider version bump

The version remains unchanged at "0.0.8". While this aligns with the PR objectives, which don't mention any version updates, it's worth considering:

1. Adding a new dependency (chokidar) could be seen as a significant change that warrants a version bump, especially if it affects the project's functionality or dependencies.
2. If you decide to bump the version, follow semantic versioning principles. For a new dependency, you might want to increment the minor version (e.g., 0.1.0) or the patch version (e.g., 0.0.9) depending on the impact of the change.

Would you like to update the version number in this PR, or do you prefer to keep it unchanged for now?

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 874f1cc and 96751da.

📒 Files selected for processing (1)

• v1/package.json (2 hunks)

🧰 Additional context used

🔇 Additional comments (1)

v1/package.json (1)

3-5: Approve addition of chokidar, but suggest reordering

The addition of "chokidar" as a dependency aligns with the PR objectives. However, I have a few suggestions:

1. To maintain consistency, consider moving "chokidar" to maintain alphabetical order within the dependencies section.

2. The AI summary mentions that a previous entry for "chokidar" was removed, but this is not visible in the provided diff. Could you please verify if there was indeed a previous entry that was removed?

To verify the previous "chokidar" entry and check the ordering, please run the following script:

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 96751da and f8b41be.

⛔ Files ignored due to path filters (2)

• v1/data/addresses.json is excluded by !v1/data/**
• v1/data/addresses.mainnet.json is excluded by !v1/data/**

📒 Files selected for processing (1)

• v1/hardhat.config.ts (1 hunks)

🧰 Additional context used

🪛 GitHub Check: lint

v1/hardhat.config.ts

[failure] 94-94:
Delete ⏎

[CryptoFewka]

@fadeev / anyone: I'm not sure that a hard dependency on "chokidar" is correct.