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

docs(simapp): update CHANGELOG to proper version #22739

Merged
merged 1 commit into from
Dec 3, 2024

Conversation

aljo242
Copy link
Contributor

@aljo242 aljo242 commented Dec 3, 2024

Description

Closes: #XXXX


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • New Features

    • Introduced new SDK modules: epochs, accounts, and protocolpool.
    • Added address codec functionality for enhanced client and signing contexts.
    • Included an example for defining a custom mint function.
  • Improvements

    • Updated module path to a new vanity URL.
    • Enhanced export function with the new module collections API.
    • Updated testnet command to align with new module APIs.
    • Refactored simulations for improved performance.
  • Bug Fixes

    • Adjusted signature for UpgradeHandler to improve compatibility.

@aljo242 aljo242 requested review from facundomedica, julienrbrt and a team as code owners December 3, 2024 21:50
Copy link
Contributor

coderabbitai bot commented Dec 3, 2024

📝 Walkthrough

Walkthrough

The pull request updates the changelog for the SimApp from version v0.50 to v0.52, detailing significant changes such as the introduction of new SDK modules, removal of the crisis module, and updates to various functions and APIs. Key modifications include a new module path, updated export functions, and refactored simulations. Additionally, the upgrade handler's method signature has been changed, and compatibility with CometBFT v1 has been ensured.

Changes

File/Path Change Summary
simapp/CHANGELOG.md Updated to reflect changes from version v0.50 to v0.52, including new modules and removed crisis module.
simapp/mint_fn.go Added example for defining a custom mint function.
x/upgrade/types Updated method signature for UpgradeHandler to accept appmodule.VersionMap.
Various files related to APIs Updated APIs for compatibility with CometBFT v1 and integration of public key types in base.Account.
app.go Refactored to use GetNodeHomeDirectory and DefaultNodeHome, and abstracted version update method.
genutilcli.Commands Updated to utilize genutil modules from the module manager.
Simulation files Refactored to use testutil/sims instead of runsims.
Testnet command Updated to align with new module APIs.

Possibly related PRs

Suggested labels

C:x/upgrade, backport/v0.52.x

Suggested reviewers

  • julienrbrt
  • sontrinh16
  • tac0turtle
  • akhilkumarpilli

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.

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.

@julienrbrt julienrbrt changed the title doc: update CHANGELOG to proper version docs: update CHANGELOG to proper version Dec 3, 2024
Copy link
Member

@julienrbrt julienrbrt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@julienrbrt julienrbrt added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Dec 3, 2024
@julienrbrt julienrbrt changed the title docs: update CHANGELOG to proper version docs(simapp): update CHANGELOG to proper version Dec 3, 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 (3)
simapp/CHANGELOG.md (3)

Line range hint 31-45: Reorganize changelog entries according to the guidelines

The changelog entries should follow the format specified in the guiding principles:

  1. Group changes by type (Features, Improvements, API Breaking, etc.)
  2. Include tags and GitHub issue references for all entries

Example structure:

### Features
* (modules) [#XXXXX] Wire new SDK modules (`epochs`, `accounts`, `protocolpool`).
* (mint) [#XXXXX] Add example of how to define a custom mint function.

### Improvements
* (client) [#XXXXX] Add address codec in client context and signing context.
* (testutil) [#20490] Refactor simulations to use `testutil/sims`.

### API Breaking
* (upgrade) [#20485] Change signature of `UpgradeHandler` to accept `appmodule.VersionMap`.

Line range hint 46-46: Clarify the TODO comment

The comment "" lacks context. Please specify:

  1. Which changelog elements need to be moved
  2. The source location of these elements
  3. The rationale for moving them

Would you like me to help track this TODO by creating a GitHub issue?


Line range hint 48-54: Consider adding brief summaries for previous versions

While linking to UPGRADING.md is helpful, consider adding brief summaries of key changes for each version. This aligns with the principle "Changelogs are for humans" and helps readers quickly understand the major changes without leaving the changelog.

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 7d11742 and e8c524b.

📒 Files selected for processing (1)
  • simapp/CHANGELOG.md (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
simapp/CHANGELOG.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

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

Line range hint 1-54: Verify all document links are valid

Let's ensure all links in the changelog are accessible.

✅ Verification successful

All links in the changelog are valid and accessible

All GitHub PR links and the UPGRADING.md reference in the changelog have been verified:

  • All 8 PR links (20409, 20485, 20740, 20771, 20490, 19726, 21466, 21508) are accessible
  • The UPGRADING.md file exists in the repository root
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that all links in the changelog are valid

# Extract and verify GitHub PR links
echo "Checking PR links..."
prLinks=$(rg -o 'https://github.com/cosmos/cosmos-sdk/pull/[0-9]+' simapp/CHANGELOG.md)
for link in $prLinks; do
  gh api "repos/cosmos/cosmos-sdk/pulls/${link##*/}" --jq '.url' || echo "Invalid PR link: $link"
done

# Verify UPGRADING.md exists
echo "Checking UPGRADING.md reference..."
test -f UPGRADING.md && echo "UPGRADING.md exists" || echo "UPGRADING.md not found"

Length of output: 1773

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants