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

[celestia-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Chores
  • Updated version identifiers across key system components to introduce a new release candidate for the main application, an enhanced core stability update, and an improved node functionality. These adjustments help maintain system performance and reliability while paving the way for future enhancements.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request updates the version tags and SHA identifiers defined in the .vitepress/constants/mocha_versions.js file. The modifications include new version strings and their associated SHA values for the app, core, and node components. No changes were made to the exported or public declarations in the file.

Changes

File Path	Change Summary
.vitepress/constants/mocha_versions.js	Updated app-latest-tag from "v3.4.0-mocha" to "v3.4.1-mocha" with a new SHA; modified core-latest-tag from "v1.49.0-tm-v0.34.35" to "v1.50.0-tm-v0.34.35" with an updated SHA; changed node-latest-tag from "v0.21.7-mocha" to "v0.21.8-mocha" with an associated SHA update.

Possibly related PRs

• Update mocha_versions.js #1829: Directly updates the same version tags and SHA identifiers in the mocha_versions.js file.
• [GH Action] Update release tags and commit SHAs for mocha #1817: Involves updates to version tags and SHA identifiers for the app-latest-tag and core-latest-tag in the same file.
• [GH Action] Update release tags and commit SHAs for mocha #1917: Updates version tags and SHAs in the same mocha_versions.js file as the main PR.

Poem

Oh, I’m hopping through the lines of code so free,
Updating tags and SHAs, as swift as can be.
From mocha to mocha, the versions do change,
With a gentle rabbit touch, everything’s in range.
In the digital meadow, my code leaps with glee!
🐇✨
Hop along and review, for improvement is our decree!

---

📜 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 99ce796 and 11261ca.

📒 Files selected for processing (1)

• .vitepress/constants/mocha_versions.js (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 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.6.0
🚀 View preview at https://celestiaorg.github.io/docs-preview/pr-1927/
Built to branch main at 2025-03-12 17:15 UTC. Preview will be ready when the GitHub Pages deployment is complete.