Skip to content

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

Merged
jcstein merged 2 commits intomainfrom
create-pull-request/patch
Jun 26, 2024
Merged

[GH Action] Update release tags and commit SHAs for mainnet#1630
jcstein merged 2 commits intomainfrom
create-pull-request/patch

Conversation

@celestia-bot
Copy link
Copy Markdown
Contributor

@celestia-bot celestia-bot commented Jun 26, 2024

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • New Features
    • Updated mainnet version constants with new version tags and SHA values for improved app, core, and node components.

@celestia-bot celestia-bot force-pushed the create-pull-request/patch branch from d7e84c6 to 088ac49 Compare June 26, 2024 14:38
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Jun 26, 2024

Warning

Review failed

The pull request is closed.

Walkthrough

The mainnet version constants in mainnet_versions.js have been updated. This includes new version tags and SHA values for the app, core, and node components. The update introduces two new sets of changes: one moving the app to version v2.0.0-rc2 and another to v1.11.0, alongside adjustments to the core and node component versions to v1.37.0 and v0.14.0 respectively.

Changes

Files Change Summary
.vitepress/constants/mainnet_versions.js Updated mainnetVersions for app, core, and node with new tags and SHA values.

Poem

🌟 In files where constants dwell,
The versions rise, it's clear to tell.
From apps to cores, nodes' array,
New tags and SHAs bright the way.
Versions jump and bugs do flee,
A smoother path for all to see! 🚀


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
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 Configration 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
Copy link
Copy Markdown
Contributor

github-actions bot commented Jun 26, 2024

PR Preview Action v1.4.7
🚀 Deployed preview to https://celestiaorg.github.io/docs-preview/./pr-1630/
on branch main at 2024-06-26 14:41 UTC

Comment thread .vitepress/constants/mainnet_versions.js Outdated
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 ed9f715 and 088ac49.

Files selected for processing (1)
  • .vitepress/constants/mainnet_versions.js (1 hunks)
Files skipped from review due to trivial changes (1)
  • .vitepress/constants/mainnet_versions.js

Comment thread .vitepress/constants/mainnet_versions.js Outdated
Comment thread .vitepress/constants/mainnet_versions.js Outdated
Comment thread .vitepress/constants/mainnet_versions.js Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants