Skip to content

chore: prep release#23349

Merged
julienrbrt merged 5 commits into
mainfrom
julien/mod
Jan 13, 2025
Merged

chore: prep release#23349
julienrbrt merged 5 commits into
mainfrom
julien/mod

Conversation

@julienrbrt
Copy link
Copy Markdown
Contributor

@julienrbrt julienrbrt commented Jan 13, 2025

Description


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

  • Dependency Updates

    • Updated cosmossdk.io/api dependency from v0.8.0 to v0.8.1 across multiple modules
    • Removed local replace directive for cosmossdk.io/api in some modules
    • Updated Protobuf tool version from 0.15.2 to 0.15.3
  • Changelog

    • Added new version entry for store/v2 (v2.0.0-beta.2)
  • Test Data

    • Modified timeout_timestamp field to null in some test data files

@julienrbrt julienrbrt requested a review from a team January 13, 2025 15:37
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jan 13, 2025

📝 Walkthrough

Walkthrough

This pull request involves multiple updates across various modules in the Cosmos SDK. The primary changes include updating the cosmossdk.io/api dependency from version v0.8.0 to v0.8.1 across numerous go.mod files, modifying some test data files with changes to the timeout_timestamp field, and updating the Protobuf version in the build scripts. These changes appear to be part of a coordinated update across the SDK's components.

Changes

File Change Summary
client/v2/autocli/testdata/*.golden Modified timeout_timestamp from a specific date to null
**/go.mod Updated cosmossdk.io/api from v0.8.0 to v0.8.1
scripts/build/protobuf.mk Updated protoVer from 0.15.2 to 0.15.3
store/v2/CHANGELOG.md Added new version entry for v2.0.0-beta.2

Possibly related PRs

Suggested Labels

C:server/v2 appmanager, C:server/v2 stf, backport/v0.52.x

Suggested Reviewers

  • kocubinski
  • sontrinh16
  • testinginprod
  • tac0turtle

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

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.

Comment thread scripts/init-simapp-v2.sh Outdated
Co-authored-by: Marko <marko@baricevic.me>
Copy link
Copy Markdown
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

🧹 Nitpick comments (3)
x/bank/go.mod (1)

Line range hint 186-187: Track TODO comment for future module separation.

The TODO comment indicates pending work to remove the replace directives after spinning out all modules.

Would you like me to create a GitHub issue to track this TODO item?

x/protocolpool/go.mod (1)

Line range hint 186-190: Track TODO comment for future module separation.

The TODO comment indicates pending work to remove the replace directives after spinning out all modules.

Would you like me to create a GitHub issue to track this TODO item?

client/v2/autocli/testdata/msg-output.golden (1)

1-1: LGTM - Consistent handling of unset timeout

The change maintains consistency with the previous file, standardizing the representation of unset timeouts as null instead of Unix epoch. This is a more semantically correct approach.

Consider updating the API documentation to explicitly mention that timeout_timestamp is nullable and what null values mean in this context.

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9ca815c and 0c063ec.

⛔ Files ignored due to path filters (26)
  • client/v2/go.sum is excluded by !**/*.sum
  • go.sum is excluded by !**/*.sum
  • server/v2/cometbft/go.sum is excluded by !**/*.sum
  • simapp/v2/go.sum is excluded by !**/*.sum
  • tests/go.sum is excluded by !**/*.sum
  • tools/benchmark/go.sum is excluded by !**/*.sum
  • x/accounts/defaults/base/go.sum is excluded by !**/*.sum
  • x/accounts/defaults/lockup/go.sum is excluded by !**/*.sum
  • x/accounts/defaults/multisig/go.sum is excluded by !**/*.sum
  • x/accounts/go.sum is excluded by !**/*.sum
  • x/authz/go.sum is excluded by !**/*.sum
  • x/bank/go.sum is excluded by !**/*.sum
  • x/circuit/go.sum is excluded by !**/*.sum
  • x/consensus/go.sum is excluded by !**/*.sum
  • x/distribution/go.sum is excluded by !**/*.sum
  • x/epochs/go.sum is excluded by !**/*.sum
  • x/evidence/go.sum is excluded by !**/*.sum
  • x/feegrant/go.sum is excluded by !**/*.sum
  • x/gov/go.sum is excluded by !**/*.sum
  • x/group/go.sum is excluded by !**/*.sum
  • x/mint/go.sum is excluded by !**/*.sum
  • x/nft/go.sum is excluded by !**/*.sum
  • x/protocolpool/go.sum is excluded by !**/*.sum
  • x/slashing/go.sum is excluded by !**/*.sum
  • x/staking/go.sum is excluded by !**/*.sum
  • x/upgrade/go.sum is excluded by !**/*.sum
📒 Files selected for processing (30)
  • client/v2/autocli/testdata/flatten-output.golden (1 hunks)
  • client/v2/autocli/testdata/msg-output.golden (1 hunks)
  • client/v2/go.mod (1 hunks)
  • go.mod (1 hunks)
  • scripts/build/protobuf.mk (1 hunks)
  • server/v2/cometbft/go.mod (1 hunks)
  • simapp/v2/go.mod (1 hunks)
  • store/v2/CHANGELOG.md (1 hunks)
  • tests/go.mod (1 hunks)
  • tools/benchmark/go.mod (1 hunks)
  • x/accounts/defaults/base/go.mod (1 hunks)
  • x/accounts/defaults/lockup/go.mod (1 hunks)
  • x/accounts/defaults/multisig/go.mod (1 hunks)
  • x/accounts/go.mod (1 hunks)
  • x/authz/go.mod (1 hunks)
  • x/bank/go.mod (1 hunks)
  • x/circuit/go.mod (1 hunks)
  • x/consensus/go.mod (1 hunks)
  • x/distribution/go.mod (1 hunks)
  • x/epochs/go.mod (1 hunks)
  • x/evidence/go.mod (1 hunks)
  • x/feegrant/go.mod (1 hunks)
  • x/gov/go.mod (1 hunks)
  • x/group/go.mod (1 hunks)
  • x/mint/go.mod (1 hunks)
  • x/nft/go.mod (1 hunks)
  • x/protocolpool/go.mod (1 hunks)
  • x/slashing/go.mod (1 hunks)
  • x/staking/go.mod (1 hunks)
  • x/upgrade/go.mod (1 hunks)
✅ Files skipped from review due to trivial changes (14)
  • x/evidence/go.mod
  • x/mint/go.mod
  • scripts/build/protobuf.mk
  • x/upgrade/go.mod
  • x/nft/go.mod
  • x/authz/go.mod
  • x/staking/go.mod
  • x/accounts/defaults/base/go.mod
  • x/accounts/defaults/lockup/go.mod
  • x/feegrant/go.mod
  • x/epochs/go.mod
  • client/v2/go.mod
  • x/gov/go.mod
  • x/distribution/go.mod
🧰 Additional context used
📓 Path-based instructions (2)
store/v2/CHANGELOG.md (1)

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

tests/go.mod (1)

Pattern tests/**/*: "Assess the integration and e2e test code assessing sufficient code coverage for the changes associated in the pull request"

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Summary
🔇 Additional comments (15)
store/v2/CHANGELOG.md (1)

28-32: LGTM! Changelog follows standard format and properly documents breaking changes.

The changelog entry for v2.0.0-beta.2 is well-structured and includes proper references to the relevant pull requests.

tools/benchmark/go.mod (1)

6-6: LGTM! API version update is consistent with other modules.

The update of cosmossdk.io/api to v0.8.1 aligns with the PR objectives and maintains consistency across modules.

x/consensus/go.mod (1)

6-6: LGTM! API version update is consistent with other modules.

The update of cosmossdk.io/api to v0.8.1 aligns with the PR objectives and maintains consistency across modules.

x/bank/go.mod (1)

6-6: LGTM! API version update is consistent with other modules.

The update of cosmossdk.io/api to v0.8.1 aligns with the PR objectives and maintains consistency across modules.

x/protocolpool/go.mod (1)

6-6: LGTM! API version update is consistent with other modules.

The update of cosmossdk.io/api to v0.8.1 aligns with the PR objectives and maintains consistency across modules.

x/slashing/go.mod (1)

6-6: LGTM: API version update is consistent.

The update of cosmossdk.io/api to v0.8.1 aligns with the coordinated version bump across modules.

x/circuit/go.mod (1)

6-6: LGTM: API version update is consistent.

The update of cosmossdk.io/api to v0.8.1 aligns with the coordinated version bump across modules.

x/accounts/defaults/multisig/go.mod (1)

21-21: LGTM: API version update is consistent.

The update of the indirect dependency cosmossdk.io/api to v0.8.1 aligns with the coordinated version bump across modules.

x/accounts/go.mod (1)

6-6: LGTM: API version update is consistent.

The update of cosmossdk.io/api to v0.8.1 aligns with the coordinated version bump across modules.

x/group/go.mod (1)

6-6: LGTM: API version update is consistent.

The update of cosmossdk.io/api to v0.8.1 aligns with the coordinated version bump across modules.

go.mod (1)

6-6: LGTM! Version update is consistent.

The update of cosmossdk.io/api to v0.8.1 aligns with the PR objectives.

server/v2/cometbft/go.mod (1)

17-17: LGTM! Version is consistent with main module.

The update of cosmossdk.io/api to v0.8.1 matches the version in the main go.mod file.

tests/go.mod (1)

6-6: LGTM! Version is consistent with main module.

The update of cosmossdk.io/api to v0.8.1 matches the version in the main go.mod file.

simapp/v2/go.mod (1)

6-6: LGTM! Version is consistent with main module.

The update of cosmossdk.io/api to v0.8.1 matches the version in the main go.mod file.

client/v2/autocli/testdata/flatten-output.golden (1)

1-1: Verify alignment with API changes

The change from Unix epoch timestamp to null for timeout_timestamp appears to be a more accurate representation of an unset timeout. However, we should verify this change aligns with the API update mentioned in the PR objectives.

Let's check for related changes in the API:

✅ Verification successful

Change from Unix epoch to null is correct

The change aligns with the protocol definition where timeout_timestamp is explicitly marked as nullable. Since this transaction has unordered=false, a null timeout is valid as timeouts are only mandatory for unordered transactions.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for timeout_timestamp related changes in proto files and API definitions
rg -g '*.proto' -g '*.go' 'timeout_timestamp' 

Length of output: 5073

@julienrbrt julienrbrt added this pull request to the merge queue Jan 13, 2025
Merged via the queue into main with commit 3586e39 Jan 13, 2025
@julienrbrt julienrbrt deleted the julien/mod branch January 13, 2025 17:17
@julienrbrt
Copy link
Copy Markdown
Contributor Author

@Mergifyio backport release/v0.52.x

@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented Jan 13, 2025

backport release/v0.52.x

✅ Backports have been created

Details

mergify Bot pushed a commit that referenced this pull request Jan 13, 2025
Co-authored-by: Marko <marko@baricevic.me>
(cherry picked from commit 3586e39)

# Conflicts:
#	client/v2/go.mod
#	client/v2/go.sum
#	go.mod
#	server/v2/cometbft/go.mod
#	server/v2/cometbft/go.sum
#	simapp/v2/go.mod
#	simapp/v2/go.sum
#	tests/go.mod
#	tools/benchmark/go.mod
#	tools/benchmark/go.sum
#	x/accounts/defaults/base/go.mod
#	x/accounts/defaults/base/go.sum
#	x/accounts/defaults/lockup/go.mod
#	x/accounts/defaults/lockup/go.sum
#	x/accounts/defaults/multisig/go.mod
#	x/accounts/defaults/multisig/go.sum
#	x/accounts/go.mod
#	x/accounts/go.sum
#	x/authz/go.mod
#	x/authz/go.sum
#	x/bank/go.mod
#	x/bank/go.sum
#	x/circuit/go.mod
#	x/circuit/go.sum
#	x/consensus/go.mod
#	x/consensus/go.sum
#	x/distribution/go.mod
#	x/distribution/go.sum
#	x/epochs/go.mod
#	x/epochs/go.sum
#	x/evidence/go.mod
#	x/evidence/go.sum
#	x/feegrant/go.mod
#	x/feegrant/go.sum
#	x/gov/go.mod
#	x/gov/go.sum
#	x/group/go.mod
#	x/group/go.sum
#	x/mint/go.mod
#	x/mint/go.sum
#	x/nft/go.mod
#	x/nft/go.sum
#	x/params/CHANGELOG.md
#	x/protocolpool/go.mod
#	x/protocolpool/go.sum
#	x/slashing/go.mod
#	x/slashing/go.sum
#	x/staking/go.mod
#	x/staking/go.sum
#	x/upgrade/go.mod
#	x/upgrade/go.sum
@mergify mergify Bot mentioned this pull request Jan 13, 2025
12 tasks
julienrbrt added a commit that referenced this pull request Jan 13, 2025
Co-authored-by: Julien Robert <julien@rbrt.fr>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants