docs: bump mocha/arabica go version

[jcstein]

Overview

Summary by CodeRabbit

• New Features

  • Updated version numbers for golangNodeMocha, golangNodeArabica, golangApp, and golangCore to reflect the latest enhancements.

• Bug Fixes

  • Ensured that versioning is consistent across components, improving overall stability.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes involve updating the version numbers for several constants in the constants.js file. Specifically, golangNodeMocha and golangNodeArabica have been incremented from "1.22.0" to "1.23.0", while golangApp and golangCore have been updated from "1.22.0" to "1.22.6". The constant golang remains unchanged. These updates reflect version increments for specific components.

Changes

File	Change Summary
.../constants/constants.js	Updated golangNodeMocha and golangNodeArabica versions from "1.22.0" to "1.23.0"; updated golangApp and golangCore from "1.22.0" to "1.22.6". golang remains unchanged.

Sequence Diagram(s)

(No sequence diagrams generated as the changes are too simple.)

Poem

🐇 In the meadow where the flowers sway,
Two nodes have danced and found their way.
From "twenty-two" to "twenty-three,"
A hop of joy, so wild and free!
With each new version, we leap and cheer,
For brighter paths are drawing near! 🌼✨

---

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

[github-actions]

PR Preview Action v1.4.7
🚀 Deployed preview to https://celestiaorg.github.io/docs-preview/./pr-1698/
on branch main at 2024-09-06 10:48 UTC

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4d656cc and 6cc924d.

Files selected for processing (1)

• .vitepress/constants/constants.js (1 hunks)

Additional comments not posted (2)

.vitepress/constants/constants.js (2)

3-3: Updated version for golangNodeMocha.

The version number for golangNodeMocha has been updated to "1.23.0". This change appears to align with the PR's objective to reflect the latest compatible Go version. Ensure that this version is indeed the latest and compatible with the project requirements.

---

4-4: Updated version for golangNodeArabica.

The version number for golangNodeArabica has been updated to "1.23.0". Similar to the previous comment, verify that this version update is accurate and reflects the latest compatible Go version for the Arabica node.

[jcstein]

@rootulp does this conflict with the version required for app v2.1.2?

[jcstein]

Suggested change

	golangCore: "1.22.0",
	golangCore: "1.22.6",