Update network-upgrade-process.md

[jcstein]

Overview

Summary by CodeRabbit

• Documentation
  • Updated the guide on the Celestia network upgrade process, clarifying breaking vs. non-breaking upgrades.
  • Expanded details on network upgrade coordination, including methods for the Lemongrass and Ginger upgrades.
  • Introduced the in-protocol signaling mechanism for validators to indicate readiness for upgrades.
  • Emphasized the importance of timely software upgrades for validators.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request updates the document on the Celestia network upgrade process, detailing the coordination and implementation of upgrades. It clarifies the distinction between breaking and non-breaking upgrades and emphasizes the necessity for validators to upgrade their software. The document expands on the methods for coordinating upgrades, including pre-programmed heights for the Lemongrass upgrade and in-protocol signaling for future upgrades. It outlines the step-by-step upgrade process, introduces the Ginger upgrade, and modifies warnings regarding the use of the cosmovisor tool.

Changes

File	Change Summary
how-to-guides/network-upgrade-process.md	Updated to include details on the Celestia network upgrade process, including coordination methods, upgrade steps, and specifics about the Lemongrass and Ginger upgrades.

Possibly related PRs

• docs: Lemongrass hardfork #1641: Updates documentation related to the Lemongrass hardfork, referenced in the main PR.
• docs: clarify no cosmovisor #1663: Clarifies that Cosmovisor is not required for the Lemongrass upgrade, aligning with the main PR's emphasis.
• docs: arabica upgrade height #1666: Discusses the Lemongrass hardfork with instructions for node operators, relevant to the upgrade process.
• docs: mocha upgrade height #1672: Updates hardfork process documentation for the Mocha upgrade, discussing similar upgrade heights and processes.
• docs: change heading to "lemongrass network upgrade" #1714: Changes headings in hardfork process documentation to reflect the Lemongrass upgrade, pertinent to the main PR.
• docs: warning for cosmovisor #1722: Emphasizes that Cosmovisor is not needed for the Lemongrass upgrade, reinforcing the main PR's focus.
• docs: add ginger upgrade to docs, update links #1758: Adds information about the Ginger upgrade, mentioned in the main PR.

Suggested labels

documentation, enhancement

Suggested reviewers

• rootulp
• cmwaters

🐰 In the meadow where upgrades bloom,
The Celestia network finds more room.
With signaling clear and processes bright,
Validators ready, all set for flight!
From Lemongrass to Ginger, a hop, skip, and cheer,
Together we flourish, the future is near! 🌼

---

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>, 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 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.4.8
🚀 Deployed preview to https://celestiaorg.github.io/docs-preview/./pr-1767/
on branch main at 2024-10-24 13:25 UTC