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: cometbft not up to date #1568

Merged
merged 2 commits into from
Sep 4, 2024

Conversation

yihuang
Copy link
Collaborator

@yihuang yihuang commented Sep 4, 2024

update to 0.38.12

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

  • Documentation

    • Updated the CHANGELOG.md to include details about the cometbft library version update to 0.38.12.
  • Dependency Updates

    • Upgraded various dependencies, including:
      • github.com/cometbft/cometbft to v0.38.12
      • github.com/cosmos/gogoproto to v1.7.0
      • github.com/spf13/cobra to v1.8.1
      • github.com/spf13/viper to v1.19.0
      • golang.org/x/crypto to v0.26.0
      • Other indirect dependencies updated for improved performance and security.

@yihuang yihuang requested a review from a team as a code owner September 4, 2024 06:43
@yihuang yihuang requested review from JayT106, thomas-nguy and mmsqe and removed request for a team September 4, 2024 06:43
Copy link
Contributor

coderabbitai bot commented Sep 4, 2024

Walkthrough

The changes involve updates to dependency versions across multiple files, including CHANGELOG.md, go.mod, and gomod2nix.toml. These updates include minor version increments for libraries such as cometbft, gogoproto, cobra, and viper, as well as several other dependencies. The modifications enhance documentation and ensure that the project utilizes the latest stable versions of its dependencies.

Changes

Files Change Summary
CHANGELOG.md Added entry for updating cometbft to version 0.38.12, including a reference to the associated pull request.
go.mod, gomod2nix.toml Updated multiple dependencies to newer versions, including cometbft, gogoproto, cobra, viper, and others.

Poem

In the meadow, I hop with glee,
New versions dance, as bright as can be!
Libraries fresh, all spruced up tight,
A happy rabbit in the moonlight!
With every change, we leap and cheer,
For smoother paths, the future is near! 🐇✨


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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

CHANGELOG.md Outdated Show resolved Hide resolved
Signed-off-by: yihuang <huang@crypto.com>
Copy link
Collaborator

@mmsqe mmsqe left a comment

Choose a reason for hiding this comment

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

Copy link

codecov bot commented Sep 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.12%. Comparing base (14779fb) to head (fed0414).
Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##             main    #1568       +/-   ##
===========================================
+ Coverage   15.24%   36.12%   +20.88%     
===========================================
  Files          67       97       +30     
  Lines        4874     7725     +2851     
===========================================
+ Hits          743     2791     +2048     
- Misses       4037     4585      +548     
- Partials       94      349      +255     

see 47 files with indirect coverage changes

@yihuang yihuang added this pull request to the merge queue Sep 4, 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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 14779fb and fed0414.

Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
Files selected for processing (3)
  • CHANGELOG.md (1 hunks)
  • go.mod (7 hunks)
  • gomod2nix.toml (12 hunks)
Files skipped from review due to trivial changes (1)
  • CHANGELOG.md
Additional comments not posted (28)
go.mod (7)

22-22: Approved version update.

The minor version update to github.com/cometbft/cometbft from v0.38.11 to v0.38.12 is approved. It likely includes bug fixes or performance improvements.


25-25: Approved version update.

The minor version update to github.com/cosmos/gogoproto from v1.4.12 to v1.7.0 is approved. It likely includes enhancements or new features.


40-42: Approved version updates.

The minor version updates to github.com/spf13/cobra from v1.8.0 to v1.8.1 and github.com/spf13/viper from v1.18.2 to v1.19.0 are approved. They likely include bug fixes or performance improvements.


45-45: Approved version update with potential critical security updates.

The substantial version update to golang.org/x/crypto from v0.22.0 to v0.26.0 is approved. It may include critical security updates, so it's important to review the changelog and update accordingly.


53-56: Approved version updates.

The minor version updates to cloud.google.com/go from v0.112.0 to v0.112.1 and cloud.google.com/go/storage from v1.37.0 to v1.38.0 are approved. They likely include bug fixes or performance improvements.


191-194: Approved version updates.

The minor version updates to github.com/prometheus/client_golang from v1.20.0 to v1.20.1, github.com/prometheus/common from v0.52.2 to v0.55.0, and github.com/prometheus/procfs from v0.15.0 to v0.15.1 are approved. They likely include bug fixes, performance improvements, enhancements, or new features.


223-241: Approved version updates with potential critical updates.

The version updates to the golang.org/x packages, including crypto, net, oauth2, sync, sys, term, text, and tools, are approved. The substantial version changes may include critical security updates, enhancements, or new features, so it's important to review the changelogs and update accordingly.

The minor version updates to the google.golang.org packages, including api and genproto, are also approved. They likely include bug fixes or performance improvements.

gomod2nix.toml (21)

5-6: LGTM!

The changes to update the module version and hash look good.


8-9: LGTM!

The changes to update the module version and hash look good.


14-15: LGTM!

The changes to update the module version and hash look good.


111-112: LGTM!

The changes to update the module version and hash look good.


114-115: LGTM!

The changes to update the module version and hash look good.


117-118: LGTM!

The changes to update the module version and hash look good.


138-139: LGTM!

The changes to update the module version and hash look good.


154-155: LGTM!

The changes to update the module version and hash look good.


180-181: LGTM!

The changes to update the module version and hash look good.


350-351: LGTM!

The changes to update the module version and hash look good.


359-360: LGTM!

The changes to update the module version and hash look good.


440-441: LGTM!

The changes to update the module version and hash look good.


487-489: LGTM!

The changes to add a new module look good.


500-501: LGTM!

The changes to update the module version and hash look good.


512-513: LGTM!

The changes to update the module version and hash look good.


518-519: LGTM!

The changes to update the module version and hash look good.


521-522: LGTM!

The changes to update the module version and hash look good.


530-531: LGTM!

The changes to update the module version and hash look good.


557-558: LGTM!

The changes to update the module version and hash look good.


563-564: LGTM!

The changes to update the module version and hash look good.


628-629: LGTM!

The changes to update the module version and hash look good.

Merged via the queue into crypto-org-chain:main with commit 90d0698 Sep 4, 2024
42 checks passed
@yihuang yihuang deleted the cometbft-update branch September 4, 2024 08:00
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