Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: v1.4.0 not released #1711

Merged
merged 2 commits into from
Dec 2, 2024
Merged

Problem: v1.4.0 not released #1711

merged 2 commits into from
Dec 2, 2024

Conversation

yihuang
Copy link
Collaborator

@yihuang yihuang commented Dec 2, 2024

Changes between rc6 and main branch:

v1.4.0-rc6...main
crypto-org-chain/cosmos-sdk@3300cc8...6031e79

👮🏻👮🏻👮🏻 !!!! 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

Summary by CodeRabbit

  • Documentation

    • Updated the changelog to include new entries for version v1.4.0 and previous release candidates, detailing significant bug fixes and improvements.
  • Bug Fixes

    • Included a fix for the iavl prune bug and updated dependencies for improved performance.

@yihuang yihuang requested a review from a team as a code owner December 2, 2024 07:18
@yihuang yihuang requested review from calvinaco and thomas-nguy and removed request for a team December 2, 2024 07:18
Copy link
Contributor

coderabbitai bot commented Dec 2, 2024

Walkthrough

The pull request updates the CHANGELOG.md to include a new entry for version v1.4.0, dated December 2, 2024. This entry details improvements related to the reproduction of an iavl prune bug in tests, a change in the iavl dependency back to upstream, and a fix for the prune command with async pruning. It also summarizes previous entries for version v1.4.0-rc6, highlighting relevant bug fixes and improvements across multiple release candidates leading up to v1.4.0.

Changes

File Change Summary
CHANGELOG.md Updated for version v1.4.0 with details on iavl prune bug improvements and dependency changes. Previous entries for v1.4.0-rc6 included bug fixes and updates related to iavl and ibc-go.

Possibly related PRs

Suggested reviewers

  • calvinaco
  • mmsqe

🐇 In the changelog, we hop with glee,
New fixes and features, oh what a spree!
IAVL's prune bug, now put to the test,
With upstream changes, we’re surely the best!
So let’s celebrate, with carrots and cheer,
For version v1.4.0, the best time of year! 🥕


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

@yihuang yihuang requested a review from mmsqe December 2, 2024 07:18
Copy link
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

🧹 Outside diff range and nitpick comments (1)
CHANGELOG.md (1)

3-3: Convert emphasis to proper heading format.

The date should use heading syntax instead of emphasis to maintain consistency with markdown standards.

Apply this diff:

-*Dec 2, 2024*
+### Dec 2, 2024
🧰 Tools
🪛 Markdownlint (0.35.0)

3-3: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 82fb523 and ade900e.

📒 Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
🧰 Additional context used
🪛 Markdownlint (0.35.0)
CHANGELOG.md

3-3: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

🔇 Additional comments (1)
CHANGELOG.md (1)

3-10: LGTM! The changelog entry follows the standard format.

The new entry for v1.4.0 is well-structured and provides clear information about the improvements made.

🧰 Tools
🪛 Markdownlint (0.35.0)

3-3: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

@yihuang yihuang enabled auto-merge December 2, 2024 07:26
@yihuang yihuang added this pull request to the merge queue Dec 2, 2024
Copy link
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

🧹 Outside diff range and nitpick comments (1)
CHANGELOG.md (1)

3-12: Verify changelog entries against PR objectives.

The changelog entries for v1.4.0 appear consistent with the PR objectives. However, there are a few formatting improvements that could be made:

Consider updating the unordered list style to use asterisks (*) instead of dashes (-) for consistency with the rest of the document:

-  - Reproduce iavl prune bug in test
-  - change iavl dependency back to upstream
-  - fix prune command with async pruning
+  * Reproduce iavl prune bug in test
+  * change iavl dependency back to upstream
+  * fix prune command with async pruning
🧰 Tools
🪛 Markdownlint (0.35.0)

10-10: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


11-11: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


12-12: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


3-3: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between ade900e and c7ed233.

📒 Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
🧰 Additional context used
🪛 Markdownlint (0.35.0)
CHANGELOG.md

10-10: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


11-11: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


12-12: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


3-3: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

Merged via the queue into crypto-org-chain:main with commit 89ecd5b Dec 2, 2024
32 checks passed
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