Skip to content

fix: update node version to latest on Mainnet beta (to be merged after Mocha is upgraded, and Mainnet has been upgraded)#1523

Merged
jcstein merged 3 commits intocelestiaorg:mainfrom
EdgarBarrantes:patch-1
Apr 22, 2024
Merged

fix: update node version to latest on Mainnet beta (to be merged after Mocha is upgraded, and Mainnet has been upgraded)#1523
jcstein merged 3 commits intocelestiaorg:mainfrom
EdgarBarrantes:patch-1

Conversation

@EdgarBarrantes
Copy link
Copy Markdown
Contributor

@EdgarBarrantes EdgarBarrantes commented Apr 12, 2024

Overview

Quick update. Almost installed the old node version :)

Summary by CodeRabbit

  • New Features
    • Updated the node version to enhance performance and compatibility.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 12, 2024

Walkthrough

The update involves a minor adjustment to the project's configuration. The node-latest-tag value has been modified from "v0.13.2" to "v0.13.4" in the mainnetVersions constant, ensuring alignment with the latest node version.

Changes

File Path Change Summary
.vitepress/constants/mainnet_versions.js Updated node-latest-tag from "v0.13.2" to "v0.13.4"

Poem

🐇✨
In the realm of code, where bits and bytes play,
A subtle tweak dances, in the light of day.
From .2 to .4, a leap so slight,
Keeping our tech ever bright.
Cheers to the devs, with code as their hunch,
Each change a step, in the grand tech bunch! 🥕🎉


Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between d685e6b and 5c3eeb1.
Files selected for processing (1)
  • .vitepress/constants/mainnet_versions.js (1 hunks)
Additional comments not posted (1)
.vitepress/constants/mainnet_versions.js (1)

6-7: The updates to the node-latest-tag and node-latest-sha are correctly implemented as per the PR discussions.

Ensure that the SHA 13ac02fe9a659b8741c2f62fac256c4ef249b718 corresponds to the tag v0.13.4 by verifying it against the project's repository or official release notes.


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
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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

@EdgarBarrantes EdgarBarrantes changed the title Update mainnet_versions.js fix: update node version to latest Apr 12, 2024
Comment thread .vitepress/constants/mainnet_versions.js Outdated
@jcstein jcstein changed the title fix: update node version to latest fix: update node version to latest on Mainnet beta Apr 12, 2024
Comment thread .vitepress/constants/mainnet_versions.js Outdated
@jcstein jcstein changed the title fix: update node version to latest on Mainnet beta fix: update node version to latest on Mainnet beta (to be merged after Mocha is upgraded, and Mainnet has been upgraded) Apr 12, 2024
@jcstein jcstein marked this pull request as draft April 12, 2024 21:50
@jcstein jcstein added the documentation Improvements or additions to documentation label Apr 12, 2024
Comment thread .vitepress/constants/mainnet_versions.js Outdated
Comment thread .vitepress/constants/mainnet_versions.js Outdated
@EdgarBarrantes
Copy link
Copy Markdown
Contributor Author

Thanks for the review! Saw v0.13.4 was published, is it live now / should we push this?

@jcstein jcstein marked this pull request as ready for review April 22, 2024 17:51
@jcstein jcstein merged commit 4a0f543 into celestiaorg:main Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants