Skip to content

fix vendoring #2069

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

Merged
merged 1 commit into from
Aug 5, 2025
Merged

fix vendoring #2069

merged 1 commit into from
Aug 5, 2025

Conversation

motatoes
Copy link
Contributor

@motatoes motatoes commented Aug 5, 2025

ran go mod tidy on each go.mod in the repo to fix #2068

closes #2068
(hopefully)

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

Greptile Summary

This PR addresses vendoring issues across the entire Digger Go workspace by updating dependencies and reorganizing module structures. The changes span 13+ modules including backend, CLI, enterprise edition components, and utility libraries.

Key changes include:

  • Dependency version updates: Major updates to github.com/samber/lo (v1.39.0 → v1.46.0), GORM packages (v1.25.11 → v1.25.12), Sentry Go SDK (v0.28.0 → v0.29.0), and various other libraries
  • Workspace reorganization: The go.work file was restructured to move Next.js modules (./next and ./next/dbgen) to the end of the workspace configuration
  • Module dependency cleanup: The ee/cli module removed unnecessary backend dependencies, reducing its footprint by eliminating web framework and database-related transitive dependencies
  • New functionality additions: The dgctl module gained GitHub API integration capabilities with direct dependencies on github.com/google/go-github/v61 and configuration management via github.com/spf13/viper
  • Database tooling updates: The next/dbgen module shifted from MySQL-focused to PostgreSQL-focused code generation with updated GORM drivers
  • Checksum synchronization: All go.sum files were updated with new checksums to ensure dependency integrity across the workspace

The changes integrate with Digger's multi-module workspace architecture, where consistent dependency versions are crucial for avoiding conflicts between the various components (backend API, CLI tools, enterprise features, and utility libraries). The workspace uses Go's module system to manage these interdependencies while allowing each module to maintain its specific requirements.

Confidence score: 2/5

  • This PR contains a critical issue that could break builds and compromise security
  • Score significantly lowered due to the completely empty go.sum file in the background/projects-refresh-service module
  • Pay close attention to background/projects-refresh-service/go.sum which is empty and will cause dependency integrity issues

17 files reviewed, no comments

Edit Code Review Bot Settings | Greptile

Copy link
Contributor

bismuthdev bot commented Aug 5, 2025

Bismuth completed its review and found no issues.

@motatoes motatoes merged commit dbd8c2a into develop Aug 5, 2025
12 checks passed
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.

Vendoring broken in 0.6.115
1 participant