build(deps): bump cosmossdk.io/log from 1.3.1 to 1.4.0

[dependabot]

Bumps cosmossdk.io/log from 1.3.1 to 1.4.0.

Commits

• 6b4557d chore: prepare log v1.4.0 (#21197)
• 5a08833 build(deps): Bump golang.org/x/crypto from 0.25.0 to 0.26.0 (#21189)
• 655b303 build(deps): Bump github.com/spf13/cast from 1.6.0 to 1.7.0 (#21190)
• cc25f59 ci: add compat check 052 x main (#21174)
• 5b7d8b6 test(stf/mock): Unmarshal with knowing the message type (#21178)
• 641f964 ci: attempt to fix goreleaser (#21194)
• a0fdab2 test(server/v2): Update testdata prune options (#21192)
• 4b4ec47 build(deps): Bump bufbuild/buf-setup-action from 1.35.1 to 1.36.0 (#21191)
• feb0e07 feat: [ADR-071] Cryptography v2 (#18824)
• 111a999 docs: rename v2 to di (#21181)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by CodeRabbit

• Chores
  • Updated dependencies to the latest stable versions for improved security, performance, and compatibility.

[coderabbitai]

Walkthrough

Walkthrough

The recent updates to the go.mod file reflect an effort to enhance the project's dependency management by upgrading several key libraries. The versions of golang.org/x/sys, cosmossdk.io/log, and github.com/rs/zerolog have been incremented, which may introduce important enhancements, bug fixes, and new features. These changes aim to ensure improved security, performance, and compatibility with the latest stable releases of these dependencies.

Changes

Files	Change Summary
go.mod	Updated dependencies:
	- golang.org/x/sys from v0.20.0 to v0.22.0
	- cosmossdk.io/log from v1.3.1 to v1.4.0
	- github.com/rs/zerolog from v1.32.0 to v1.33.0

---

Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7b481bd and 89a480f.

Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

Files selected for processing (1)

• go.mod (3 hunks)

Additional comments not posted (3)

go.mod (3)

150-150: Verify logging functionality with cosmossdk.io/log update.

The update from v1.3.1 to v1.4.0 may introduce changes in logging behavior. Verify that all logging functionality works as expected.

---

26-26: Verify compatibility of golang.org/x/sys update.

The update from v0.20.0 to v0.22.0 may include important changes. Ensure that the codebase is compatible with this version.

Verification successful

---

No direct or indirect usage of golang.org/x/sys found.

The search did not reveal any direct or indirect usage of the golang.org/x/sys package in the codebase. This suggests that the update to version v0.22.0 might not directly impact the current code. However, since it is marked as an indirect dependency, it is still advisable to verify compatibility through testing or checking with any dependencies that might use it.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify compatibility of `golang.org/x/sys` update.

# Test: Check for any breaking changes or incompatibilities in the codebase.
rg --type go --fixed-strings 'golang.org/x/sys'

Length of output: 47

---

Script:

#!/bin/bash
# Description: Check for indirect usage of `golang.org/x/sys` in dependencies.

# List all Go files to check for any imports that might use `golang.org/x/sys` indirectly.
fd --type f --extension go --exec rg --context 5 'import' {}

Length of output: 45977

---

198-198: Verify zerolog usage with updated version.

The update from v1.32.0 to v1.33.0 may introduce changes. Ensure that all logging functionality using zerolog is functioning correctly.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.