Problem: v1.4.0-rc4 is not released

[yihuang]

RELEASE NOTES

v1.4.0-rc4 is not non-consensus-breaking upgrade against rc3, it enables async-pruning feature in iavl v1 to fix the node hanging issue we faced when upgrade testnet, also includes a versiondb tool to fix a data corruption issue.

👮🏻👮🏻👮🏻 !!!! REFERENCE THE PROBLEM YOUR ARE SOLVING IN THE PR TITLE AND DESCRIBE YOUR SOLUTION HERE !!!! DO NOT FORGET !!!! 👮🏻👮🏻👮🏻

PR Checklist:

• Have you read the CONTRIBUTING.md?
• Does your PR follow the C4 patch requirements?
• Have you rebased your work on top of the latest master?
• Have you checked your code compiles? (make)
• Have you included tests for any non-trivial functionality?
• Have you checked your code passes the unit tests? (make test)
• Have you checked your code formatting is correct? (go fmt)
• Have you checked your basic code style is fine? (golangci-lint run)
• If you added any dependencies, have you checked they do not contain any known vulnerabilities? (go list -json -m all | nancy sleuth)
• If your changes affect the client infrastructure, have you run the integration test?
• If your changes affect public APIs, does your PR follow the C4 evolution of public contracts?
• If your code changes public APIs, have you incremented the crate version numbers and documented your changes in the CHANGELOG.md?
• If you are contributing for the first time, please read the agreement in CONTRIBUTING.md now and add a comment to this pull request stating that your PR is in accordance with the Developer's Certificate of Origin.

Thank you for your code, it's appreciated! :)

Summary by CodeRabbit

• Bug Fixes

  • Resolved issues related to corrupted data in the version database.
  • Fixed insufficient balance reporting with no trace detail.

• Improvements

  • Enhanced versiondb with a new key-value store accepting string names.
  • Introduced a Timestamp API for the versiondb iterator.
  • Added an asynchronous pruning option for improved performance.

• Documentation

  • Updated CHANGELOG.md to reflect changes in version v1.4.0-rc4 and previous releases.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The CHANGELOG.md file has been updated to document the release of version v1.4.0-rc4, dated November 14, 2024. This update includes bug fixes, such as a command for addressing corrupted data and a fix for insufficient balance trace details. Improvements feature enhancements to the versiondb, including a new string parameter for NewKVStore, a Timestamp API for iterators, and an asynchronous pruning option for iavl. The changelog also includes records of previous versions, maintaining a structured documentation of changes across releases.

Changes

File	Change Summary
CHANGELOG.md	Updated to reflect release of version v1.4.0-rc4 with bug fixes and improvements. Includes details of previous version v1.4.0-rc3.

Possibly related PRs

• Problem: v1.4.0-rc3 not released #1675: Updates CHANGELOG.md for version v1.4.0-rc3, documenting changes leading to v1.4.0-rc4.
• Problem: no trace detail on insufficient balance fix is not included #1679: Addresses the inclusion of no trace detail on the insufficient balance fix mentioned in the main PR.
• Problem: iavl v1 pruning takes a long time #1692: Includes updates to CHANGELOG.md with improvements and bug fixes related to versiondb.
• Problem: iavl rollback not tested #1693: Discusses testing rollback functionality in the iavl implementation, relevant to improvements in the main PR.

Suggested reviewers

• mmsqe
• devashishdxt

🐇 In the changelog, we hop with glee,
Version v1.4.0-rc4, as bright as can be!
Bug fixes and features, all in a row,
Documenting changes, watch our progress grow!
With each little tweak, our project takes flight,
A rabbit's delight, everything feels right! 🌟

---

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.