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

Mark v1.20.0-rc3. #2193

Merged
merged 1 commit into from
Oct 18, 2024
Merged

Mark v1.20.0-rc3. #2193

merged 1 commit into from
Oct 18, 2024

Conversation

SpicyLemon
Copy link
Contributor

@SpicyLemon SpicyLemon commented Oct 18, 2024

Description

This PR marks v1.20.0-rc3 in main.

It's basically a frontport of this PR:


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against correct branch (see CONTRIBUTING.md).
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Wrote unit and integration tests
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/).
  • Added relevant godoc comments.
  • Added relevant changelog entries under .changelog/unreleased (see Adding Changes).
  • Re-reviewed Files changed in the Github PR explorer.
  • Review Codecov Report in the comment section below once CI passes.

Summary by CodeRabbit

  • Bug Fixes

    • Resolved an issue causing nodes to fail to restart after being stopped post-upgrade.
    • Removed parameters store key and transient store key to enhance application stability.
  • Documentation

    • Updated the CHANGELOG.md with new release notes for version v1.20.0-rc3, including links to previous versions and a full commit history.

* Add a bit to the summary.

* Mark v1.20.0-rc3
@SpicyLemon SpicyLemon requested a review from a team as a code owner October 18, 2024 16:11
Copy link
Contributor

coderabbitai bot commented Oct 18, 2024

Walkthrough

This pull request involves the removal of the parameters store key and transient store key from the application, as documented in a deleted changelog entry. The CHANGELOG.md file has been updated to reflect new release notes for version v1.20.0-rc3, which includes this removal as a bug fix addressing an issue from version v1.20.0-rc2. The changelog also provides a comprehensive commit history and details on features, improvements, and breaking changes across multiple versions.

Changes

File Path Change Summary
.changelog/unreleased/bug-fixes/2189-remove-params-storekey.md Deleted file documenting the removal of parameters store key and transient store key.
CHANGELOG.md Updated to include new release notes for v1.20.0-rc3, including links to previous versions.

Possibly related PRs

Suggested reviewers

  • scirner22
  • iramiller

Poem

In the code where bunnies hop,
Keys were lost, but we won't stop.
With each release, we fix and mend,
Changelog updates, on us depend.
Hopping forward, we cheer with glee,
For a smoother path, just wait and 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>, 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.

@SpicyLemon SpicyLemon enabled auto-merge (squash) October 18, 2024 16:12
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)

Line range hint 1-228: Changelog structure and formatting review.

The changelog is well-structured overall, but there are some areas for improvement:

  1. Consistency: Ensure consistent formatting across all entries. For example, some entries use full sentences with periods, while others don't.

  2. Links: While many entries include links to issues or PRs, some don't. Consider adding links to all relevant issues/PRs for better traceability.

  3. Versioning: The versioning scheme is clear, with release candidates (RC) properly labeled.

  4. Categorization: The use of categories (Features, Improvements, Bug Fixes, etc.) is helpful for quick reference.

  5. Markdown usage: The markdown formatting is generally good, but ensure all lists are properly indented for better readability.

Consider running a markdown linter to catch any formatting inconsistencies. For example:

#!/bin/bash
# Run markdownlint on the CHANGELOG.md file
npx markdownlint-cli CHANGELOG.md

This will help maintain a consistent and readable changelog.

🧰 Tools
🪛 Markdownlint

64-64: null
Bare URL used

(MD034, no-bare-urls)


65-65: null
Bare URL used

(MD034, no-bare-urls)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 5f0c4e9 and b2a8821.

📒 Files selected for processing (2)
  • .changelog/unreleased/bug-fixes/2189-remove-params-storekey.md (0 hunks)
  • CHANGELOG.md (1 hunks)
💤 Files with no reviewable changes (1)
  • .changelog/unreleased/bug-fixes/2189-remove-params-storekey.md
🧰 Additional context used
🪛 Markdownlint
CHANGELOG.md

64-64: null
Bare URL used

(MD034, no-bare-urls)


65-65: null
Bare URL used

(MD034, no-bare-urls)

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

55-65: New release v1.20.0-rc3 with bug fix and commit history.

The changelog entry for v1.20.0-rc3 includes:

  1. A bug fix addressing an issue from v1.20.0-rc2.
  2. Links to the full commit history.

Some observations:

  • The bug fix removes the params store key and transient store key from the app, resolving a problem that prevented nodes from restarting if stopped after the upgrade.
  • The full commit history is provided via GitHub comparison links, which is helpful for developers who want to see all changes in detail.
🧰 Tools
🪛 Markdownlint

64-64: null
Bare URL used

(MD034, no-bare-urls)


65-65: null
Bare URL used

(MD034, no-bare-urls)


Line range hint 67-80: v1.20.0-rc2 release with bug fixes and commit history.

The changelog entry for v1.20.0-rc2 includes:

  1. Two bug fixes:
    • Renaming the RELEASE_NOTES.md file to RELEASE_CHANGELOG.md
    • Fixing the heighliner build
  2. Links to the full commit history

Observations:

  • The bug fixes seem minor but could be important for maintaining consistency in documentation and build processes.
  • The full commit history is again provided via GitHub comparison links, maintaining transparency and traceability.
🧰 Tools
🪛 Markdownlint

64-64: null
Bare URL used

(MD034, no-bare-urls)


65-65: null
Bare URL used

(MD034, no-bare-urls)


Line range hint 1-228: Overall assessment of the CHANGELOG.md file.

The CHANGELOG.md file is a valuable resource for users and developers of the Provenance blockchain. It provides a comprehensive history of changes, improvements, and bug fixes across multiple versions.

Strengths:

  1. Chronological order with the most recent changes at the top.
  2. Clear versioning, including release candidates.
  3. Categorization of changes (Features, Improvements, Bug Fixes, etc.).
  4. Links to GitHub issues and pull requests for many entries.
  5. Inclusion of both major and minor changes.

Areas for potential improvement:

  1. Consistency in formatting and level of detail across entries.
  2. Ensuring all entries have links to relevant issues or pull requests.
  3. More consistent use of markdown formatting for better readability.

Despite these minor areas for improvement, the changelog effectively communicates the project's evolution and helps users understand what to expect in each new version.

To maintain and improve the quality of the changelog, consider implementing a changelog entry checklist for contributors, ensuring that each new entry follows a consistent format and includes all necessary information.

🧰 Tools
🪛 Markdownlint

64-64: null
Bare URL used

(MD034, no-bare-urls)


65-65: null
Bare URL used

(MD034, no-bare-urls)


Line range hint 82-228: Comprehensive v1.20.0-rc1 release with significant changes and updates.

This release includes numerous changes across various categories:

  1. Features:

    • Creation of the 'viridian' upgrade
    • Changes to NAV (Net Asset Value) handling
    • Addition of the circuit breaker module
  2. Improvements:

    • Multiple module parameter migrations
    • Removal of legacy proposals and unused code
    • Updates to various dependencies
  3. Bug Fixes:

    • Several fixes related to proto generation, CLI commands, and module behaviors
  4. Client Breaking Changes:

    • Removal of old provwasm bindings
    • Changes to some proto enum values
  5. API Breaking Changes:

    • Changes to query behaviors in the metadata module
    • Removal of the params module
  6. Dependencies:

    • Numerous updates to various dependencies, including Cosmos SDK, CosmWasm, and others

Key points to note:

  • The removal of legacy code and migration of parameters could improve overall system efficiency.
  • The addition of the circuit breaker module may enhance system safety.
  • API and client breaking changes should be clearly communicated to users to ensure smooth transitions.
  • The extensive dependency updates suggest improved security and performance, but thorough testing is crucial.

To ensure all breaking changes are properly documented and communicated:

🧰 Tools
🪛 Markdownlint

64-64: null
Bare URL used

(MD034, no-bare-urls)


65-65: null
Bare URL used

(MD034, no-bare-urls)

@SpicyLemon SpicyLemon merged commit 0bf059c into main Oct 18, 2024
20 checks passed
@SpicyLemon SpicyLemon deleted the dwedul/v1.20.0-rc3-to-main branch October 18, 2024 16:23
@coderabbitai coderabbitai bot mentioned this pull request Nov 21, 2024
8 tasks
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.

3 participants