Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency bumps: node 18 to 22 #403

Merged
merged 1 commit into from
Feb 28, 2025
Merged

Dependency bumps: node 18 to 22 #403

merged 1 commit into from
Feb 28, 2025

Conversation

jaybuidl
Copy link
Member

@jaybuidl jaybuidl commented Feb 28, 2025

PR-Codex overview

This PR updates the node version in multiple package.json files from 18.20.7 to 22.14.0, ensuring compatibility with newer features and improvements.

Detailed summary

  • Updated node version from 18.20.7 to 22.14.0 in the following files:
    • relayer-cli/package.json
    • validator-cli/package.json
    • contracts/package.json
    • relayer-subgraph-inbox/package.json
    • veascan-subgraph-inbox/package.json
    • veascan-subgraph-outbox/package.json
    • veascan-web/package.json
    • package.json

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Summary by CodeRabbit

Summary by CodeRabbit

  • Chores
    • Upgraded the project’s runtime environment to Node.js version 22.14.0 across multiple components, ensuring improved consistency and compatibility.

Copy link
Contributor

coderabbitai bot commented Feb 28, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request updates the Node.js version specified in the volta sections across several package.json files. The version is changed from "18.20.7" to "22.14.0" in multiple components including contracts, CLI tools, subgraphs, and the web interface. The engines requirement remains unchanged, ensuring that Node.js versions from 18.0.0 onward continue to be supported.

Changes

File(s) Change Summary
contracts/package.json, package.json, relayer-cli/package.json, relayer-subgraph-inbox/package.json, validator-cli/package.json, veascan-subgraph-inbox/package.json, veascan-subgraph-outbox/package.json Updated Node.js version in the "volta" section from "18.20.7" to "22.14.0".
veascan-web/package.json Updated Node.js version in the "volta" section from "18.20.7" to "22.14.0"; yarn version remains unchanged.

Poem

I'm a clever rabbit with nimble paws,
Leaping into code with joyful cheers,
Upgrading Node to 22 without pause,
Hopping past old bugs and outdated fears,
Carrots and new code—springtime appears!


📜 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 57a0e2a and 31643e3.

📒 Files selected for processing (8)
  • contracts/package.json (1 hunks)
  • package.json (1 hunks)
  • relayer-cli/package.json (1 hunks)
  • relayer-subgraph-inbox/package.json (1 hunks)
  • validator-cli/package.json (1 hunks)
  • veascan-subgraph-inbox/package.json (1 hunks)
  • veascan-subgraph-outbox/package.json (1 hunks)
  • veascan-web/package.json (1 hunks)

🪧 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 or @coderabbitai title 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.

Copy link

netlify bot commented Feb 28, 2025

Deploy Preview for veascan failed. Why did it fail? →

Name Link
🔨 Latest commit 31643e3
🔍 Latest deploy log https://app.netlify.com/sites/veascan/deploys/67c2171bec0509000841d75f

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
validator-cli/package.json (1)

23-23: Upgrade to ethers v6 in CLI Dependency
The dependency on "@typechain/ethers-v6": "^0.5.1" indicates the switch to ethers v6 as part of the CLI packages update. Please verify that this change does not introduce breaking changes in any CLI functionalities that interact with the Ethereum blockchain. Thorough regression tests and integration checks are recommended.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b5b3083 and 57a0e2a.

📒 Files selected for processing (8)
  • contracts/package.json (1 hunks)
  • package.json (1 hunks)
  • relayer-cli/package.json (1 hunks)
  • relayer-subgraph-inbox/package.json (1 hunks)
  • validator-cli/package.json (1 hunks)
  • veascan-subgraph-inbox/package.json (1 hunks)
  • veascan-subgraph-outbox/package.json (1 hunks)
  • veascan-web/package.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (5)
  • GitHub Check: Redirect rules - veascan
  • GitHub Check: Header rules - veascan
  • GitHub Check: Pages changed - veascan
  • GitHub Check: dependency-review
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (8)
relayer-cli/package.json (1)

7-9: Node Version Upgrade in Volta Configuration
The Node version in the volta section has been updated from the previous value to "22.14.0". This upgrade aligns with the overall repository update to Node 22. Please ensure that all CLI tooling and scripts in this package are compatible with Node 22.

relayer-subgraph-inbox/package.json (1)

7-9: Update Node Version in Volta Section
The volta configuration now specifies "node": "22.14.0", which standardizes the development environment across packages. Confirm that any graph CLI commands or subgraph tooling continue to function correctly with Node 22.

veascan-subgraph-inbox/package.json (1)

7-10: Standardizing the Node Environment
The Node version change to "22.14.0" in the volta section ensures consistency with other subgraph packages. It is advisable to run a smoke test for subgraph code generation and deployment to ensure full compatibility with Node 22.

veascan-subgraph-outbox/package.json (1)

7-10: Volta Node Version Update
The updated volta configuration now specifies "node": "22.14.0", aligning this package with the newer Node.js environment. Make sure that all scripts, especially those related to builds and deployments, are validated against Node 22.

validator-cli/package.json (1)

7-10: Node Version Consistency for Validator CLI
The volta section here has been updated to "node": "22.14.0", which maintains consistency across CLI packages. Ensure that any Node-specific behavior in this CLI is re-tested under Node 22.

package.json (1)

28-30: Update Node.js Version in Volta Config
The volta configuration has been updated from Node.js 18.20.7 to 22.14.0. This change is consistent with the project-wide upgrade outlined in the PR objectives. Please verify that all CLI tools and scripts relying on this configuration are compatible with Node 22.

veascan-web/package.json (1)

16-18: Consistent Node.js Version Bump in Volta
The Node.js version in the volta field has been updated to "22.14.0", matching the project's new standard. Ensure that any Node.js–specific code within this package is tested against Node 22 to catch potential compatibility issues.

contracts/package.json (1)

24-26: Update Node.js Version and Ethers Dependency
The volta section now reflects Node.js "22.14.0", which aligns with the overall update across the project. Additionally, the ethers dependency in devDependencies is now at "^6.13.5", effectively bumping it to version 6 as intended. Verify that all deployments and contract interactions remain stable under these new versions.

@jaybuidl jaybuidl changed the title Dependency bumps: node 18 to 22, ethers to v6 in CLI packages Dependency bumps: node 18 to 22 Feb 28, 2025
@jaybuidl jaybuidl force-pushed the chore/node-ethers-upgrades branch from 57a0e2a to 31643e3 Compare February 28, 2025 20:05
@jaybuidl jaybuidl merged commit 31643e3 into dev Feb 28, 2025
5 of 7 checks passed
@jaybuidl jaybuidl deleted the chore/node-ethers-upgrades branch February 28, 2025 20:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants