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

[celestia-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features
  • Updated application, core, and node versions to enhance functionality and performance.
  • New version tags reflect the latest improvements and features.
• Bug Fixes
  • Version updates may include critical bug fixes for improved stability.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes involve updates to the mainnetVersions constant in the .vitepress/constants/mainnet_versions.js file. Specifically, the application, core, and node versions have been incremented, along with their corresponding SHA hashes. These updates indicate a progression in software versions, reflecting enhancements or fixes in functionality and security.

Changes

Files	Change Summary
.vitepress/constants/mainnet_versions.js	Updated mainnetVersions constant: application version changed from v1.11.0 to v1.13.0, core version from v1.38.0-tm-v0.34.29 to v1.40.1-tm-v0.34.29-rc0, and node version from v0.14.1 to v0.15.0. Corresponding SHA hashes were also modified.

Sequence Diagram(s)

(no diagram generated as changes are straightforward)

Poem

In the code where bunnies play,
Versions hop in bright array.
From v1.11 to v1.13,
New features gleam, oh what a scene!
With SHA in tow, they leap and bound,
Chasing bugs, they won't be found! 🐇✨

---

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 as 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.

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

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-1686/
on branch main at 2024-08-26 15:43 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 a8f6631 and 28f4db1.

Files selected for processing (1)

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

Additional comments not posted (6)

.vitepress/constants/mainnet_versions.js (6)

2-2: LGTM!

The application version tag has been correctly updated to v2.1.2.

The code change is approved.

---

3-3: LGTM!

The application SHA hash has been correctly updated to 48173df3dc78f9348eedb3796f29ef9e9e5dc584.

The code change is approved.

---

4-4: LGTM!

The core version tag has been correctly updated to v1.40.1-tm-v0.34.29-rc0.

The code change is approved.

---

5-5: LGTM!

The core SHA hash has been correctly updated to 0d2b63836d0f4587e162bfded58f53fba238e69c.

The code change is approved.

---

6-6: LGTM!

The node version tag has been correctly updated to v0.16.1-rc0.

The code change is approved.

---

7-7: LGTM!

The node SHA hash has been correctly updated to 9fd66a56132d25957fd25116ca548343fee0f3c4.

The code change is approved.