[GH Action] Update release tags and commit SHAs for mocha

[celestia-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Documentation
  • Updated the documentation to reflect the latest version information for core and node components.

[coderabbitai]

Walkthrough

The recent update involves modifications to the mocha_versions.js file within the .vitepress/constants directory, aimed at updating version information for Mocha. This includes changes to the latest tags and SHA identifiers for both the core and node environments, ensuring that the documentation or application remains current with the latest Mocha developments.

Changes

File Path	Change Summary
.vitepress/.../mocha_versions.js	Updated core-latest-tag, core-latest-sha, node-latest-tag, and node-latest-sha versions

🐰✨
In the realm of endless code, where versions rise and fall,
A rabbit hopped through lines so bold, to update versions, big and small.
With a flick of its ear, and a click of its paw,
The latest tags and SHAs, within .vitepress now law.
Let's celebrate these changes, with joy and cheer,
For progress marches on, with every passing year.
🚀🌟

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-tests for this file.
• 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 tests 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 from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @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.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[github-actions]

PR Preview Action v1.4.7
🚀 Deployed preview to https://celestiaorg.github.io/docs/pr-preview/pr-1422/
on branch gh-pages at 2024-02-19 12:16 UTC

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 87ab003 and ca018ca.

Files selected for processing (1)

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

Additional comments: 1

.vitepress/constants/mocha_versions.js (1)

• 4-7: The updates to core-latest-tag, core-latest-sha, node-latest-tag, and node-latest-sha appear to be correctly formatted and follow the existing structure of the file. However, it's important to verify that these new version tags and SHAs accurately correspond to the latest releases of Mocha for both core and Node.js versions. This verification is crucial to ensure that the project references the correct and intended versions of Mocha.

It's also recommended to document the process or automate the verification of these version updates in the future to streamline the maintenance and ensure accuracy.

[jcstein]

cc @mindstyle85