Update github.com/diggerhq/digger/next digest to fd83543

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
github.com/diggerhq/digger/next	require	digest	5834969 -> fd83543

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ Artifact update notice

File name: ee/drift/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 42 additional dependencies were updated

Details:

Package	Change
github.com/diggerhq/digger/backend	v0.0.0-20241111093622-90aa7b8b0d00 -> v0.0.0-20241111113338-9a40639ab83c
github.com/samber/slog-gin	v1.13.3 -> v1.15.0
github.com/Azure/azure-sdk-for-go/sdk/azcore	v1.11.0 -> v1.17.0
github.com/Azure/azure-sdk-for-go/sdk/azidentity	v1.5.2 -> v1.8.0
github.com/Azure/azure-sdk-for-go/sdk/internal	v1.5.2 -> v1.10.0
github.com/AzureAD/microsoft-authentication-library-for-go	v1.2.2 -> v1.3.2
github.com/aws/aws-sdk-go-v2	v1.31.0 -> v1.32.4
github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream	v1.6.2 -> v1.6.6
github.com/aws/aws-sdk-go-v2/config	v1.27.16 -> v1.28.3
github.com/aws/aws-sdk-go-v2/credentials	v1.17.16 -> v1.17.44
github.com/aws/aws-sdk-go-v2/feature/dynamodb/attributevalue	v1.13.20 -> v1.15.15
github.com/aws/aws-sdk-go-v2/feature/dynamodb/expression	v1.7.20 -> v1.7.50
github.com/aws/aws-sdk-go-v2/feature/ec2/imds	v1.16.3 -> v1.16.19
github.com/aws/aws-sdk-go-v2/internal/configsources	v1.3.18 -> v1.3.23
github.com/aws/aws-sdk-go-v2/internal/endpoints/v2	v2.6.18 -> v2.6.23
github.com/aws/aws-sdk-go-v2/internal/ini	v1.8.0 -> v1.8.1
github.com/aws/aws-sdk-go-v2/internal/v4a	v1.3.7 -> v1.3.23
github.com/aws/aws-sdk-go-v2/service/cognitoidentity	v1.26.3 -> v1.27.5
github.com/aws/aws-sdk-go-v2/service/dynamodb	v1.32.6 -> v1.36.5
github.com/aws/aws-sdk-go-v2/service/dynamodbstreams	v1.20.8 -> v1.24.5
github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding	v1.11.2 -> v1.12.0
github.com/aws/aws-sdk-go-v2/service/internal/checksum	v1.3.9 -> v1.4.4
github.com/aws/aws-sdk-go-v2/service/internal/endpoint-discovery	v1.9.8 -> v1.10.4
github.com/aws/aws-sdk-go-v2/service/internal/presigned-url	v1.11.9 -> v1.12.4
github.com/aws/aws-sdk-go-v2/service/internal/s3shared	v1.17.7 -> v1.18.4
github.com/aws/aws-sdk-go-v2/service/s3	v1.54.3 -> v1.66.3
github.com/aws/aws-sdk-go-v2/service/sso	v1.20.9 -> v1.24.5
github.com/aws/aws-sdk-go-v2/service/ssooidc	v1.24.3 -> v1.28.4
github.com/aws/aws-sdk-go-v2/service/sts	v1.28.10 -> v1.32.4
github.com/aws/smithy-go	v1.21.0 -> v1.22.0
github.com/dineshba/tf-summarize	v0.3.10 -> v0.3.14
github.com/go-sql-driver/mysql	v1.7.0 -> v1.8.1
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
github.com/jackc/pgservicefile	v0.0.0-20221227161230-091c0ba34f0a -> v0.0.0-20231201235250-de7065d80cb9
github.com/stretchr/testify	v1.9.0 -> v1.10.0
golang.org/x/crypto	v0.28.0 -> v0.32.0
golang.org/x/net	v0.30.0 -> v0.34.0
golang.org/x/sync	v0.8.0 -> v0.10.0
golang.org/x/sys	v0.26.0 -> v0.29.0
golang.org/x/term	v0.25.0 -> v0.28.0
golang.org/x/text	v0.19.0 -> v0.21.0

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Join our Discord community for assistance with any issues or questions.

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 sequence diagram to generate a sequence diagram of the changes in this 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.

[greptile-apps]

PR Summary

This PR updates the digger/next dependency to a newer version (3378761) along with several other dependency updates in the ee/drift module.

• Updated github.com/diggerhq/digger/next to latest digest version in ee/drift/go.mod
• Upgraded multiple AWS SDK packages to newer versions for improved compatibility
• Updated Google Cloud Platform related dependencies with security patches
• Maintained Go 1.22.4 compatibility while updating core dependencies
• Synchronized go.sum file with cryptographic hashes for new dependency versions

_{2 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: ee/drift/go.sum

Command failed: go get -d -t ./...
go: -d flag is deprecated. -d=true is a no-op
go: downloading github.com/diggerhq/digger/backend v0.0.0-20241111113338-9a40639ab83c
go: github.com/diggerhq/digger/ee/drift/tasks imports
	github.com/diggerhq/digger/backend/models/dbmodels: cannot find module providing package github.com/diggerhq/digger/backend/models/dbmodels
go: warning: github.com/gabriel-vasile/mimetype@v1.4.4: retracted by module author: v1.4.4 had a test file detected as malicious by antivirus software. #575
go: to switch to the latest unretracted version, run:
	go get github.com/gabriel-vasile/mimetype@latest

[bismuthdev]

Bug Summary

Total Bugs Found: 1

Critical Bug

• Invalid Go Module Version Format: In the ee/drift/go.mod file, the module version for github.com/diggerhq/digger/next is using an invalid format (just a commit hash). This will cause issues with Go's module system and dependency resolution, potentially breaking builds or causing unexpected behavior when other modules try to depend on this one.

[bismuthdev]

The module version format for github.com/diggerhq/digger/next is invalid. Go modules require a specific version format, and using just a commit hash (e42e96520391) is not valid.

For commit hashes, Go requires using a pseudo-version format like v0.0.0-yyyymmddhhmmss-commithash. The correct format should be something like v0.0.0-20240611120391-e42e96520391 where the middle part is a timestamp and the last part is the commit hash.

This invalid version format will cause issues with Go's module system and dependency resolution, potentially breaking builds or causing unexpected behavior when other modules try to depend on this one.

Suggested change

	github.com/diggerhq/digger/next e42e96520391
	github.com/diggerhq/digger/next v0.0.0-20240611120391-e42e96520391

[bismuthdev]

Bismuth encountered an error

[bismuthdev]

Bug Summary

Total Bugs Found: 1

Critical Bugs

1. Incorrect Go Module Dependency Format - In ee/drift/go.mod, the dependency on github.com/diggerhq/digger/next uses an incorrect format that violates Go's module versioning requirements. The dependency is missing the required version prefix format (v0.0.0-[date]-[commit hash]), which can lead to build failures and dependency resolution issues.

[bismuthdev]

The dependency on github.com/diggerhq/digger/next is specified with an incorrect format. Go modules require a specific version format for dependencies, even when using commit hashes. The correct format should be v0.0.0-[date]-[commit hash] (e.g., v0.0.0-20240000000000-fd83543ef8b7).

The current format github.com/diggerhq/digger/next fd83543ef8b7 is missing the version prefix, which violates Go's module versioning requirements. This can cause build failures or dependency resolution issues when other modules try to use this package or when running go mod tidy.

Suggested change

	github.com/diggerhq/digger/next fd83543ef8b7
	github.com/diggerhq/digger/next v0.0.0-20240000000000-fd83543ef8b7