chore: set upgrade height for testnet v8.1

[zakir-code]

Summary by CodeRabbit

• New Features

  • Added support for version 8.1 in testnet block height configuration

• Style

  • Updated version output formatting from uppercase "V" to lowercase "v" for both mainnet and testnet version displays

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces minor modifications to version output formatting in the cmd/doctor.go file and adds a new testnet block height constant in types/version.go. The changes primarily involve converting version strings from uppercase "V" to lowercase "v" for both mainnet and testnet scenarios. A new constant TestnetBlockHeightV81 is added to support version 8.1 for testnet block height tracking.

Changes

File	Change Summary
cmd/doctor.go	Updated version output strings from uppercase "V" to lowercase "v" for multiple block height conditions in mainnet and testnet
types/version.go	Added new constant TestnetBlockHeightV81 = 18_019_000 with a comment indicating version 8.1

Possibly related PRs

• feat: add v7.2 version check #488: Modification of checkBlockchainData function in cmd/doctor.go with testnet block height version check
• chore: set upgrade height for testnet v8 #857: Introduction of a new condition in checkBlockchainData for handling testnet version 8

Poem

🐰 Versions dance, from V to v they leap,
Lowercase letters now softly creep
Block heights rise, constants expand
A rabbit's code, precisely planned!
Small changes bloom with gentle might 🌱

---

📜 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 c968118 and ce023f5.

📒 Files selected for processing (2)

• cmd/doctor.go (1 hunks)
• types/version.go (1 hunks)

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.