Update modules 20250102

[noborus]

Summary by CodeRabbit

• Chores
  • Updated multiple Go module dependencies to their latest versions
  • Upgraded dependencies for gopsutil, go-yaml, and various modernc.org packages
  • Incremented versions of indirect dependencies like golang.org/x/exp

[coderabbitai]

Walkthrough

This pull request focuses on updating dependency versions in the go.mod file for the github.com/noborus/psutilsql module. The changes primarily involve incrementing versions of direct and indirect dependencies, including gopsutil, go-yaml, and several modernc.org packages. These updates likely include bug fixes, performance improvements, or minor feature enhancements across the various dependencies.

Changes

File	Change Summary
go.mod	- Updated github.com/shirou/gopsutil/v4 from v4.24.11 to v4.24.12 - Updated github.com/goccy/go-yaml from v1.15.10 to v1.15.13 - Updated indirect dependencies: golang.org/x/exp, modernc.org/gc/v3, modernc.org/libc, modernc.org/mathutil, modernc.org/sqlite, modernc.org/strutil

Poem

🐰 Dependency Dance, a Rabbit's Delight

Versions hop, modules take flight
Go.mod twirls with updates so bright
Packages leap to a newer height
Modernc and gopsutil shine their might
A coding waltz of pure delight! 🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d1bd57e and 8cd667d.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• go.mod (3 hunks)

🔇 Additional comments (3)

go.mod (3)

7-7: Verify gopsutil update compatibility

The update of github.com/shirou/gopsutil/v4 from v4.24.11 to v4.24.12 appears to be a patch version bump. Let's verify the changes and compatibility.

✅ Verification successful

✅ gopsutil v4.24.12 update is safe to proceed

The update from v4.24.11 to v4.24.12 is a safe patch version bump that includes:

• Performance improvements and code refactoring in CPU and network modules
• Bug fixes for process handling, memory leaks, and sensor issues
• No breaking changes introduced

The changes affect several files in the codebase that import gopsutil:

• CPU, disk, docker, host, load, memory, network, and process query implementations
• All changes in v4.24.12 are backwards compatible improvements

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for breaking changes in gopsutil v4.24.12

# Check if the version exists and get its release date
gh api repos/shirou/gopsutil/releases | jq '.[] | select(.tag_name=="v4.24.12") | {tag_name, published_at, body}'

# Look for any breaking changes in the codebase that might be affected
rg -l "github.com/shirou/gopsutil/v4"

Length of output: 2238

---

Line range hint 3-3: Verify Go version compatibility

The module uses Go 1.22.0, which is a recent version. Please ensure all updated dependencies are compatible with this Go version.

✅ Verification successful

Go 1.22.0 is compatible with the updated dependencies

After reviewing the go.mod file, I can confirm that the dependencies are compatible with Go 1.22.0. The key observations:

• All dependencies are using recent versions and are actively maintained
• Critical dependencies like github.com/shirou/gopsutil/v4 (v4.24.12) and modernc.org/sqlite (v1.34.4) are on their latest stable versions
• The indirect dependencies are also on recent versions that support Go 1.22.0
• No replace directives or version downgrades are present that might indicate compatibility issues

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for Go version compatibility in dependencies

# Check go.mod files in key dependencies for their Go version requirements
gh api repos/shirou/gopsutil/contents/go.mod | jq -r '.content' | base64 -d | grep "^go "
gh api repos/modernc.org/sqlite/contents/go.mod | jq -r '.content' | base64 -d | grep "^go "

Length of output: 401

---

Script:

#!/bin/bash
# Let's try a different approach to check dependencies
# First, let's see what dependencies are being updated in this PR
rg -U "require \(.*?\)" go.mod -A 10

# Also check if there are any replace directives
rg "^replace" go.mod

Length of output: 61

---

Script:

#!/bin/bash
# Let's try to see the entire go.mod file content
cat go.mod

Length of output: 2624

---

53-58: Verify SQLite-related dependency updates

Multiple modernc.org packages have been updated, which are critical for SQLite functionality:

• gc/v3: v3.0.0-20241213165251-3bc300f6d0c9 -> v3.0.0-20241223112719-96e2e1e4408d
• libc: v1.61.4 -> v1.61.6
• mathutil: v1.6.0 -> v1.7.1
• sqlite: v1.34.2 -> v1.34.4
• strutil: v1.2.0 -> v1.2.1

Let's verify these updates for compatibility and potential issues.

✅ Verification successful

Let me gather more information about the SQLite usage in the codebase.

---

Let me check one final aspect about the SQLite usage and version compatibility.

---

SQLite dependency updates appear to be indirect and safe

Based on the codebase analysis:

• The SQLite-related packages are marked as indirect dependencies
• The codebase primarily uses standard database/sql interface as seen in multiple Go files
• No direct imports or version-specific requirements of modernc.org/sqlite were found
• The project depends on go-sqlite3 as mentioned in README.md, while modernc.org/sqlite is an indirect dependency

The updates are minor version bumps (e.g., sqlite v1.34.2 -> v1.34.4) and appear to be routine maintenance updates. Since these are indirect dependencies and the codebase doesn't directly interact with them, these changes should not impact the functionality.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for SQLite-related breaking changes

# Check for SQLite usage in the codebase
rg -l "modernc.org/sqlite"

# Look for any SQL-related tests that might need verification
fd -e test.go | xargs rg "sqlite"

Length of output: 996

---

Script:

#!/bin/bash
# Check for direct SQLite usage patterns in the code
rg -l "sql\." --type go

# Look for database initialization or setup code
ast-grep --pattern 'sql.Open($$$)'

# Check for any migration files or schema definitions
fd -e sql

Length of output: 572

---

Script:

#!/bin/bash
# Check the main package imports and database initialization
rg -A 5 "modernc.org/sqlite|mattn/go-sqlite3" --type go

# Look at test files for any specific SQLite version requirements
rg "sqlite" psutilsql_test.go

Length of output: 87

---

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

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.