Skip to content

fix go sum entries #1920

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
Mar 25, 2025
Merged

fix go sum entries #1920

merged 1 commit into from
Mar 25, 2025

Conversation

motatoes
Copy link
Contributor

@motatoes motatoes commented Mar 25, 2025

fixes #1919

Summary by CodeRabbit

  • Chores
    • Updated various third-party libraries to improve performance, reliability, and security.
    • Removed an outdated dependency and added a new integration to streamline our overall infrastructure.

Copy link
Contributor

coderabbitai bot commented Mar 25, 2025

Walkthrough

The pull request updates dependency versions in multiple go.mod files. Several indirect dependencies have had their versions bumped across modules in different directories. Additionally, one file removes an unused dependency and adds a new one. These changes modify the dependency declarations without altering the runtime control flow.

Changes

File(s) Change Summary
backend/go.mod, cli/go.mod, ee/cli/go.mod Updated dependency versions:
github.com/dineshba/tf-summarize (v0.3.10 → v0.3.14)
github.com/hashicorp/go-getter (v1.7.4 → v1.7.8)
github.com/hashicorp/terraform-config-inspect (v0.0.0-20240509232506-4708120f8f30 → v0.0.0-20250203082807-efaa306e97b4)
• Various golang.org/x/* libraries updated
ee/backend/go.mod Removed dependency: ariga.io/atlas-provider-gorm
Updated dependency versions for:
github.com/dineshba/tf-summarize (v0.3.10 → v0.3.14)
github.com/hashicorp/go-getter (v1.7.4 → v1.7.8)
github.com/hashicorp/terraform-config-inspect (v0.0.0-20240509232506-4708120f8f30 → v0.0.0-20250203082807-efaa306e97b4)
golang.org/x/crypto, x/net, x/sys, x/term
Added dependency: github.com/ktrysmt/go-bitbucket (v0.9.81)

Poem

I'm a rabbit coding through the night,
Hopping through dependencies with delight.
Versions leap from old to new,
Unused links out, fresh bits in view.
In our code garden, I dance with glee! 🐰✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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.

@motatoes motatoes merged commit ceae074 into develop Mar 25, 2025
11 of 12 checks passed
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

🧹 Nitpick comments (1)
backend/go.mod (1)

24-24: New Dependency Addition: github.com/ktrysmt/go-bitbucket v0.9.81
A new dependency has been added in this module. Please verify that its functionality is needed, its API is compatible, and that there is no conflict with other Bitbucket-related integrations.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e40aac8 and cb9078b.

⛔ Files ignored due to path filters (6)
  • backend/go.sum is excluded by !**/*.sum
  • cli/go.sum is excluded by !**/*.sum
  • ee/backend/go.sum is excluded by !**/*.sum
  • ee/cli/go.sum is excluded by !**/*.sum
  • go.work.sum is excluded by !**/*.sum
  • libs/go.sum is excluded by !**/*.sum
📒 Files selected for processing (4)
  • backend/go.mod (4 hunks)
  • cli/go.mod (5 hunks)
  • ee/backend/go.mod (5 hunks)
  • ee/cli/go.mod (4 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Build
🔇 Additional comments (12)
backend/go.mod (4)

124-124: Dependency Version Bump: github.com/dineshba/tf-summarize
Version updated from v0.3.10 to v0.3.14 (indirect). Ensure that any functionality relying on this package does not break with the new version.


168-168: Dependency Version Bump: github.com/hashicorp/go-getter
Updated to v1.7.8. Confirm that the semantics (and any minor API differences) are compatible with your existing usage.


187-187: Dependency Version Bump: github.com/hashicorp/terraform-config-inspect
Version updated to v0.0.0-20250203082807-efaa306e97b4. Please double-check that any needed adjustments (such as handling for new API behaviors) are addressed in your code.


289-296: Golang.org/x Dependencies Update
The indirect dependencies for packages such as golang.org/x/crypto, golang.org/x/net, golang.org/x/sync, golang.org/x/sys, golang.org/x/term, and golang.org/x/text have been updated to their newer versions. These updates are consistent with changes in other modules; however, please verify that no breaking changes were introduced by these updates.

cli/go.mod (1)

1-29: Dependency Consistency in CLI Module
This module’s direct dependencies (shown in the first require block) look unaffected. Ensure that the indirect dependency versions (which are updated in related modules) propagate correctly here. In particular, after these version bumps you should run go mod tidy to update the associated go.sum entries.

ee/cli/go.mod (2)

1-19: Module Dependency Alignment for EE CLI
The direct dependency versions in the EE CLI module now match those in other modules (e.g. updated versions for libraries such as github.com/stretchr/testify and github.com/spf13/viper). No discrepancies are immediately visible here.


21-40: Indirect Dependencies Block Verification
Examine the indirect dependencies block to ensure that updates (for example, for various Azure and Google Cloud SDKs) are consistent. Since the same dependency version updates are applied in other go.mod files, it is important that the indirect dependencies are also in-sync.

ee/backend/go.mod (5)

1-8: Module Declaration and Go Version Update
The module is now declared with Go version 1.22.4. Please confirm that the new Go version is supported across your build and CI environments.


9-23: Direct Dependency Adjustments
It appears that certain dependencies (e.g. ariga.io/atlas-provider-gorm) have been removed in this module as intended. Ensure that no parts of your code still rely on the removed package before finalizing the change.


25-55: Indirect Dependency Block Consistency
Review the large block of indirect dependencies to verify that version updates are aligned with those in the backend and CLI modules. In particular, check that updates to external SDKs—such as those for Azure and Google Cloud—and the version bumps for common packages (like the golang.org/x/* updates) are consistent.


281-288: Golang.org/x Package Updates Verification
The updates for packages such as golang.org/x/crypto, golang.org/x/net, golang.org/x/sync, golang.org/x/sys, golang.org/x/term, and golang.org/x/text are also applied here. As with other modules, double-check that these updates cause no regressions.


310-315: Go Sum Update Verification
After mass dependency updates like these, it is critical to run go mod tidy so that your go.sum entries are regenerated correctly. Please verify that the new entries are committed and that no checksum errors occur during build processes.

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.

Missing go.sum entries since 0.6.92
1 participant