[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 the application version from v3.4.2 to v3.5.0.
  • Updated the node component version from v0.21.9 to v0.22.0.

[coderabbitai]

Walkthrough

This change updates the version tags and SHA identifiers in the mocha_versions.js file. The app-latest-tag is updated from "v3.4.2-mocha" to "v3.5.0-mocha" and its corresponding SHA is updated, while the node-latest-tag is updated from "v0.21.9-mocha" to "v0.22.0-mocha" along with its SHA. No public API declarations or other files have been modified.

Changes

File(s)	Change Summary
.vitepress/constants/mocha_versions.js	Updated app-latest-tag from "v3.4.2-mocha" to "v3.5.0-mocha" and updated its SHA. Similarly, updated node-latest-tag from "v0.21.9-mocha" to "v0.22.0-mocha" along with its SHA.

Possibly related PRs

• [GH Action] Update release tags and commit SHAs for mocha #1936: Updates the version tags and SHA identifiers in mocha_versions.js for similar components.
• [GH Action] Update release tags and commit SHAs for mocha #1817: Focuses on modifications to the app-latest-tag in the same file.
• Update mocha_versions.js #1933: Contains changes to the version tags and SHA identifiers in mocha_versions.js, aligning closely with the current modifications.

Suggested reviewers

• jcstein

Poem

I hop with glee in lines of code,
Updating versions along the road.
Tags and SHAs now gleam so bright,
A rabbit's joy in coding flight.
Cheers to changes—let’s crunch them right! 🐰

---

📜 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 ad5cf23 and 39eb293.

📒 Files selected for processing (1)

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

🔇 Additional comments (2)

.vitepress/constants/mocha_versions.js (2)

2-3: Version update for app component looks good.

The app version has been bumped from v3.4.2-mocha to v3.5.0-mocha with corresponding SHA update. This is a minor version increase which suggests new features were added without breaking changes.

---

6-7: Version update for node component looks good.

The node version has been bumped from v0.21.9-mocha to v0.22.0-mocha with corresponding SHA update. This represents a minor version increment which typically indicates new features without breaking API changes.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, 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-1941/
Built to branch main at 2025-03-20 15:23 UTC. Preview will be ready when the GitHub Pages deployment is complete.