Skip to content

fix(deps): update github.com/diggerhq/digger/next digest to 4a7ae74 #1912

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

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 24, 2025

This PR contains the following updates:

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

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.

Copy link
Contributor Author

renovate bot commented Mar 24, 2025

ℹ 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

Copy link
Contributor

coderabbitai bot commented Mar 24, 2025

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.

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.

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 renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to 3378761 fix(deps): update github.com/diggerhq/digger/next digest to e40aac8 Mar 25, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch from 1fde5c5 to b62e994 Compare March 25, 2025 13:27
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to e40aac8 fix(deps): update github.com/diggerhq/digger/next digest to ceae074 Mar 25, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch from b62e994 to 647cf89 Compare March 25, 2025 15:48
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to ceae074 fix(deps): update github.com/diggerhq/digger/next digest to e7504dc Mar 26, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch from 647cf89 to 278ad45 Compare March 26, 2025 16:31
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to e7504dc fix(deps): update github.com/diggerhq/digger/next digest to 28a8ecd Mar 27, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch from 278ad45 to b311a26 Compare March 27, 2025 18:58
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to 28a8ecd fix(deps): update github.com/diggerhq/digger/next digest to cfb4dc9 Mar 29, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch from b311a26 to d56d45b Compare March 29, 2025 17:35
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to cfb4dc9 fix(deps): update github.com/diggerhq/digger/next digest to 2e301b4 Apr 2, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch 2 times, most recently from 693143c to c567f42 Compare April 2, 2025 11:54
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to 2e301b4 fix(deps): update github.com/diggerhq/digger/next digest to 4c9cfb6 Apr 2, 2025
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to 4c9cfb6 fix(deps): update github.com/diggerhq/digger/next digest to 96c9822 Apr 2, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch from c567f42 to 6451b4f Compare April 2, 2025 22:20
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to 96c9822 fix(deps): update github.com/diggerhq/digger/next digest to 71aee64 Apr 4, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch 2 times, most recently from ba4fa90 to b3b50a4 Compare April 8, 2025 23:10
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to 71aee64 fix(deps): update github.com/diggerhq/digger/next digest to 8a4389b Apr 8, 2025
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to 8a4389b fix(deps): update github.com/diggerhq/digger/next digest to e03f303 Apr 15, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch from b3b50a4 to 4177c0c Compare April 15, 2025 15:52
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to e03f303 fix(deps): update github.com/diggerhq/digger/next digest to 349de90 Apr 30, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch from 4177c0c to 2c5993b Compare April 30, 2025 01:49
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to 349de90 fix(deps): update github.com/diggerhq/digger/next digest to 465edae May 7, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch from 2c5993b to c58a454 Compare May 7, 2025 02:09
ee/drift/go.mod Outdated
@@ -10,7 +10,7 @@ require (
github.com/bradleyfalzon/ghinstallation/v2 v2.11.0
github.com/diggerhq/digger/backend v0.0.0-20241111093622-90aa7b8b0d00
github.com/diggerhq/digger/libs v0.4.15
github.com/diggerhq/digger/next v0.0.0-20241111115930-58349692eece
github.com/diggerhq/digger/next cc703a9dc0c3
Copy link
Contributor

Choose a reason for hiding this comment

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

The dependency specification for github.com/diggerhq/digger/next in ee/drift/go.mod is using an invalid format. Go modules require a version prefix (like v0.0.0-) before the commit hash. The current format cc703a9dc0c3 is not a valid Go module version identifier.

The proper format should be v0.0.0-YYYYMMDDHHMMSS-cc703a9dc0c3 or similar pseudo-version. I've used a placeholder date since we can't verify the actual commit timestamp.

This invalid format would cause build errors when trying to resolve dependencies.

Suggested change
github.com/diggerhq/digger/next cc703a9dc0c3
github.com/diggerhq/digger/next v0.0.0-20240724000000-cc703a9dc0c3

@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch from 5ab7a4d to e781746 Compare July 24, 2025 07:34
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to cc703a9 fix(deps): update github.com/diggerhq/digger/next digest to 71e3c0a Jul 24, 2025
Copy link
Contributor

bismuthdev bot commented Jul 24, 2025

Bug Summary

Total Bugs Found: 1

Critical Bug

  • Invalid Go Module Dependency Format: In the ee/drift/go.mod file, the dependency for github.com/diggerhq/digger/next is using an incorrect version format. The dependency is specified with only a commit hash (71e3c0a3f4ca) instead of using a proper Go module version format, which requires either a semantic version or a pseudo-version with the appropriate prefix.

ee/drift/go.mod Outdated
@@ -10,7 +10,7 @@ require (
github.com/bradleyfalzon/ghinstallation/v2 v2.11.0
github.com/diggerhq/digger/backend v0.0.0-20241111093622-90aa7b8b0d00
github.com/diggerhq/digger/libs v0.4.15
github.com/diggerhq/digger/next v0.0.0-20241111115930-58349692eece
github.com/diggerhq/digger/next 71e3c0a3f4ca
Copy link
Contributor

Choose a reason for hiding this comment

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

The dependency version format for github.com/diggerhq/digger/next is incorrect. Go modules require a specific version format for dependencies, and using just a commit hash (71e3c0a3f4ca) without the proper pseudo-version prefix is invalid.

In Go modules, dependencies should use either:

  1. A semantic version (like v1.2.3)
  2. A pseudo-version (like v0.0.0-20240724000000-71e3c0a3f4ca) for commits without tags

The current format will cause issues with Go's module system, potentially leading to build failures or dependency resolution problems. The correct format should include the pseudo-version prefix.

Suggested change
github.com/diggerhq/digger/next 71e3c0a3f4ca
github.com/diggerhq/digger/next v0.0.0-20240724000000-71e3c0a3f4ca

@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch from e781746 to 2421561 Compare July 24, 2025 19:47
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to 71e3c0a fix(deps): update github.com/diggerhq/digger/next digest to c4be2e3 Jul 24, 2025
Copy link
Contributor

bismuthdev bot commented Jul 24, 2025

Bug Summary

Total Bugs Found: 1

Bug Summary:

  1. Invalid Go Module Dependency Format - The dependency specification for github.com/diggerhq/digger/next in ee/drift/go.mod uses an invalid format. It specifies only a commit hash (c4be2e37ed23) without the required version prefix that Go modules expect. This would cause dependency fetch failures during build or update operations.

ee/drift/go.mod Outdated
@@ -10,7 +10,7 @@ require (
github.com/bradleyfalzon/ghinstallation/v2 v2.11.0
github.com/diggerhq/digger/backend v0.0.0-20241111093622-90aa7b8b0d00
github.com/diggerhq/digger/libs v0.4.15
github.com/diggerhq/digger/next v0.0.0-20241111115930-58349692eece
github.com/diggerhq/digger/next c4be2e37ed23
Copy link
Contributor

Choose a reason for hiding this comment

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

The dependency format for github.com/diggerhq/digger/next is invalid. Go modules require a proper version format, even for pseudo-versions. The current format c4be2e37ed23 is just a commit hash without the required version prefix.

The correct format should be a pseudo-version like v0.0.0-20240724000000-c4be2e37ed23 where:

  • v0.0.0 is the version prefix
  • 20240724000000 is a timestamp (I've used today's date as a placeholder)
  • c4be2e37ed23 is the commit hash

This invalid format will cause build failures or dependency resolution issues when trying to build or update the module.

Suggested change
github.com/diggerhq/digger/next c4be2e37ed23
github.com/diggerhq/digger/next v0.0.0-20240724000000-c4be2e37ed23

ee/drift/go.mod Outdated
@@ -10,7 +10,7 @@ require (
github.com/bradleyfalzon/ghinstallation/v2 v2.11.0
github.com/diggerhq/digger/backend v0.0.0-20241111093622-90aa7b8b0d00
github.com/diggerhq/digger/libs v0.4.15
github.com/diggerhq/digger/next v0.0.0-20241111115930-58349692eece
github.com/diggerhq/digger/next c4be2e37ed23
Copy link
Contributor

Choose a reason for hiding this comment

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

The dependency specification for github.com/diggerhq/digger/next in ee/drift/go.mod is using an invalid format. Go modules require a version prefix (v0.0.0-) before the commit hash when referencing a specific commit.

The current format github.com/diggerhq/digger/next c4be2e37ed23 is incorrect and would cause dependency fetch failures. It should be formatted as github.com/diggerhq/digger/next v0.0.0-20240724000000-c4be2e37ed23 or similar with a proper pseudo-version.

Additionally, I cannot verify if the commit hash c4be2e3 actually exists in the repository due to environment limitations, but the format issue is definitely a bug regardless of whether the commit exists.

Suggested change
github.com/diggerhq/digger/next c4be2e37ed23
github.com/diggerhq/digger/next v0.0.0-20240724000000-c4be2e37ed23

@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch from 2421561 to 686168a Compare July 25, 2025 15:16
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to c4be2e3 fix(deps): update github.com/diggerhq/digger/next digest to e8a86a2 Jul 25, 2025
Copy link
Contributor

bismuthdev bot commented Jul 25, 2025

Bug Summary

Total Bugs Found: 1

Bug Details

  • Incorrect Go Module Dependency Format: In ee/drift/go.mod, the dependency for github.com/diggerhq/digger/next is specified with an incorrect format. The dependency uses a direct commit hash reference without following Go's required semantic versioning format, which should include a version prefix and date component.

ee/drift/go.mod Outdated
@@ -10,7 +10,7 @@ require (
github.com/bradleyfalzon/ghinstallation/v2 v2.11.0
github.com/diggerhq/digger/backend v0.0.0-20241111093622-90aa7b8b0d00
github.com/diggerhq/digger/libs v0.4.15
github.com/diggerhq/digger/next v0.0.0-20241111115930-58349692eece
github.com/diggerhq/digger/next e8a86a2223cc
Copy link
Contributor

Choose a reason for hiding this comment

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

The dependency for github.com/diggerhq/digger/next is specified with an incorrect format. In Go modules, dependencies should follow the semantic versioning format. When using a specific commit hash, the proper format is v0.0.0-<date>-<commit hash>.

The current format github.com/diggerhq/digger/next e8a86a2223cc is missing the version prefix and date component. This non-standard format will cause issues with Go's dependency management system, as Go expects all module versions to follow the semantic versioning format.

The correct format should be github.com/diggerhq/digger/next v0.0.0-20240725000000-e8a86a2223cc (or with the actual date of the commit instead of today's date placeholder).

This issue could lead to build failures, dependency resolution problems, and issues when other developers try to use or build the project.

Suggested change
github.com/diggerhq/digger/next e8a86a2223cc
github.com/diggerhq/digger/next v0.0.0-20240725000000-e8a86a2223cc

@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch from 686168a to efb67df Compare July 25, 2025 18:48
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to e8a86a2 fix(deps): update github.com/diggerhq/digger/next digest to 2678e75 Jul 25, 2025
Copy link
Contributor

bismuthdev bot commented Jul 25, 2025

Bug Summary

Total bugs found: 1

Critical Bug Details

  • Invalid dependency version format in ee/drift/go.mod
    • The dependency for github.com/diggerhq/digger/next uses an invalid version format (2678e7585667)
    • This format lacks the required version prefix and timestamp component that Go's module system requires
    • Will cause dependency resolution issues as Go won't be able to properly parse and resolve this dependency

ee/drift/go.mod Outdated
@@ -10,7 +10,7 @@ require (
github.com/bradleyfalzon/ghinstallation/v2 v2.11.0
github.com/diggerhq/digger/backend v0.0.0-20241111093622-90aa7b8b0d00
github.com/diggerhq/digger/libs v0.4.15
github.com/diggerhq/digger/next v0.0.0-20241111115930-58349692eece
github.com/diggerhq/digger/next 2678e7585667
Copy link
Contributor

Choose a reason for hiding this comment

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

The dependency version format for github.com/diggerhq/digger/next is invalid. Go modules require a version identifier that follows semantic versioning or a pseudo-version format.

The current format 2678e7585667 is missing the required version prefix (v0.0.0-) and timestamp component that Go expects for pseudo-versions. This will cause dependency resolution issues as Go's module system won't be able to properly parse and resolve this dependency.

The correct format should be a pseudo-version like v0.0.0-20240725000000-2678e7585667 where:

  • v0.0.0 is the version prefix
  • 20240725000000 is a timestamp (using today's date as reference)
  • 2678e7585667 is the commit hash

This format follows Go's module versioning conventions and will allow proper dependency resolution.

Suggested change
github.com/diggerhq/digger/next 2678e7585667
github.com/diggerhq/digger/next v0.0.0-20240725000000-2678e7585667

@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch from efb67df to 7a103f7 Compare July 25, 2025 19:22
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to 2678e75 fix(deps): update github.com/diggerhq/digger/next digest to 05d0425 Jul 25, 2025
Copy link
Contributor

bismuthdev bot commented Jul 25, 2025

Bug Summary

Total Bugs Found: 1

Bug Details

  • Invalid Go Module Dependency Version Format: The dependency github.com/diggerhq/digger/next in ee/drift/go.mod is using an incorrect version format (05d0425d52e2). This format doesn't follow Go's required semantic versioning or pseudo-version format, which will cause build failures or dependency resolution issues.

ee/drift/go.mod Outdated
@@ -10,7 +10,7 @@ require (
github.com/bradleyfalzon/ghinstallation/v2 v2.11.0
github.com/diggerhq/digger/backend v0.0.0-20241111093622-90aa7b8b0d00
github.com/diggerhq/digger/libs v0.4.15
github.com/diggerhq/digger/next v0.0.0-20241111115930-58349692eece
github.com/diggerhq/digger/next 05d0425d52e2
Copy link
Contributor

Choose a reason for hiding this comment

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

The dependency github.com/diggerhq/digger/next is using an invalid version format. In Go modules, versions must follow the semantic versioning format or use a pseudo-version format for commits.

The current format 05d0425d52e2 is missing the required v prefix and timestamp information that Go expects. This will cause build failures or dependency resolution issues.

The correct format should be something like v0.0.0-20240705-05d0425d52e2 where:

  • v0.0.0 is the version prefix
  • 20240705 is the date in YYYYMMDD format
  • 05d0425d52e2 is the commit hash

This follows Go's pseudo-version format for commit-based dependencies.

Suggested change
github.com/diggerhq/digger/next 05d0425d52e2
github.com/diggerhq/digger/next v0.0.0-20240705-05d0425d52e2

@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to 05d0425 fix(deps): update github.com/diggerhq/digger/next digest to 043926b Jul 25, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch from 7a103f7 to 73308c0 Compare July 25, 2025 21:44
Copy link
Contributor

bismuthdev bot commented Jul 25, 2025

Bug Summary

Total Bugs Found: 1

Critical Bug

  • Invalid Go Module Dependency Format: In the ee/drift/go.mod file, the dependency for github.com/diggerhq/digger/next uses an invalid version format (043926b20e16). This format doesn't follow Go's required semantic versioning or pseudo-version format for commit-based versions, which will cause build failures when resolving dependencies.

ee/drift/go.mod Outdated
@@ -10,7 +10,7 @@ require (
github.com/bradleyfalzon/ghinstallation/v2 v2.11.0
github.com/diggerhq/digger/backend v0.0.0-20241111093622-90aa7b8b0d00
github.com/diggerhq/digger/libs v0.4.15
github.com/diggerhq/digger/next v0.0.0-20241111115930-58349692eece
github.com/diggerhq/digger/next 043926b20e16
Copy link
Contributor

Choose a reason for hiding this comment

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

The Go module dependency format for github.com/diggerhq/digger/next is invalid. Go module versions must follow the semantic versioning format or use a pseudo-version format for commits.

The current format 043926b20e16 is missing the required v0.0.0- prefix and timestamp that Go expects for a commit-based version. The proper format should be v0.0.0-20240725043926-043926b20e16 or similar, where:

  • v0.0.0- is the prefix for pseudo-versions
  • 20240725 would be the date of the commit (or another appropriate date)
  • 043926 is the timestamp portion
  • 043926b20e16 is the commit hash

This invalid format will cause build failures when trying to resolve dependencies.

Suggested change
github.com/diggerhq/digger/next 043926b20e16
github.com/diggerhq/digger/next v0.0.0-20240725043926-043926b20e16

@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/next digest to 043926b fix(deps): update github.com/diggerhq/digger/next digest to 4a7ae74 Jul 26, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-next-digest branch from 73308c0 to f5d423f Compare July 26, 2025 09:14
Copy link
Contributor

bismuthdev bot commented Jul 26, 2025

Bismuth completed its review and found no issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants