Skip to content

Update github.com/diggerhq/digger/backend digest to fd83543 #1910

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/backend require digest 9a40639 -> fd83543
github.com/diggerhq/digger/backend require digest 90aa7b8 -> 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 these updates 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/cli/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):

  • 8 additional dependencies were updated

Details:

Package Change
github.com/bytedance/sonic v1.11.6 -> v1.11.9
github.com/gabriel-vasile/mimetype v1.4.3 -> v1.4.4
github.com/go-playground/validator/v10 v10.20.0 -> v10.22.0
github.com/jackc/pgservicefile v0.0.0-20221227161230-091c0ba34f0a -> v0.0.0-20231201235250-de7065d80cb9
github.com/jackc/pgx/v5 v5.4.3 -> v5.5.5
github.com/klauspost/cpuid/v2 v2.2.7 -> v2.2.8
golang.org/x/oauth2 v0.23.0 -> v0.24.0
gorm.io/gorm v1.25.10 -> v1.25.11
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):

  • 41 additional dependencies were updated

Details:

Package Change
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

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.


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

Updates backend dependency across multiple modules to version d07625c, along with routine maintenance updates to various indirect dependencies.

  • Updates github.com/diggerhq/digger/backend from 9a40639/90aa7b8 to d07625c in ee/backend, ee/cli, ee/drift, and next modules
  • Adds new dependency ktrysmt/go-bitbucket v0.9.81 across modules
  • Updates AWS SDK packages to v1.32.4 series
  • Updates database drivers including jackc/pgx and gorm.io/gorm to latest versions
  • Updates core golang.org/x packages including crypto, net, and sys

7 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/backend digest to d07625c fix(deps): update github.com/diggerhq/digger/backend digest to 3378761 Mar 24, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch from bb28b87 to 01d681c Compare March 24, 2025 22:56
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/backend digest to 3378761 fix(deps): update github.com/diggerhq/digger/backend digest to e40aac8 Mar 25, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch 3 times, most recently from 8f46ae0 to fd40834 Compare March 25, 2025 15:47
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/backend digest to e40aac8 fix(deps): update github.com/diggerhq/digger/backend digest to ceae074 Mar 25, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch from fd40834 to 3d2e8db Compare March 26, 2025 16:30
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/backend digest to ceae074 fix(deps): update github.com/diggerhq/digger/backend digest to e7504dc Mar 26, 2025
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/backend digest to e7504dc fix(deps): update github.com/diggerhq/digger/backend digest to 28a8ecd Mar 27, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch 2 times, most recently from 54605ce to 2903b5e Compare March 29, 2025 17:34
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/backend digest to 28a8ecd fix(deps): update github.com/diggerhq/digger/backend digest to cfb4dc9 Mar 29, 2025
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/backend digest to cfb4dc9 fix(deps): update github.com/diggerhq/digger/backend digest to 2e301b4 Apr 2, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch from 2903b5e to e0179ae Compare April 2, 2025 10:47
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/backend digest to 2e301b4 fix(deps): update github.com/diggerhq/digger/backend digest to 4c9cfb6 Apr 2, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch from e0179ae to 88a31ee Compare April 2, 2025 11:53
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/backend digest to 4c9cfb6 fix(deps): update github.com/diggerhq/digger/backend digest to 96c9822 Apr 2, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch from 88a31ee to 7c26a00 Compare April 2, 2025 22:19
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/backend digest to 96c9822 fix(deps): update github.com/diggerhq/digger/backend digest to 71aee64 Apr 4, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch 3 times, most recently from ffb2e55 to 7117607 Compare April 8, 2025 23:09
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/backend digest to 71aee64 fix(deps): update github.com/diggerhq/digger/backend digest to 8a4389b Apr 8, 2025
@renovate renovate bot changed the title fix(deps): update github.com/diggerhq/digger/backend digest to 8a4389b fix(deps): update github.com/diggerhq/digger/backend digest to e03f303 Apr 15, 2025
@renovate renovate bot changed the title Update github.com/diggerhq/digger/backend digest to 368b373 Update github.com/diggerhq/digger/backend digest to 9906efb Jul 7, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch from 02fb25a to 0531529 Compare July 7, 2025 19:00
@renovate renovate bot changed the title Update github.com/diggerhq/digger/backend digest to 9906efb Update github.com/diggerhq/digger/backend digest to 8668ee1 Jul 7, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch from 0531529 to bd50be9 Compare July 7, 2025 23:28
@renovate renovate bot changed the title Update github.com/diggerhq/digger/backend digest to 8668ee1 Update github.com/diggerhq/digger/backend digest to cddd136 Jul 10, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch 2 times, most recently from b649b9b to ff4ea8c Compare July 11, 2025 01:50
@renovate renovate bot changed the title Update github.com/diggerhq/digger/backend digest to cddd136 Update github.com/diggerhq/digger/backend digest to c565c98 Jul 11, 2025
@renovate renovate bot changed the title Update github.com/diggerhq/digger/backend digest to c565c98 Update github.com/diggerhq/digger/backend digest to 64a6f0d Jul 11, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch from ff4ea8c to 4674c27 Compare July 11, 2025 08:37
@renovate renovate bot changed the title Update github.com/diggerhq/digger/backend digest to 64a6f0d Update github.com/diggerhq/digger/backend digest to 09444ac Jul 11, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch from 4674c27 to 983c7f5 Compare July 11, 2025 22:39
@renovate renovate bot changed the title Update github.com/diggerhq/digger/backend digest to 09444ac Update github.com/diggerhq/digger/backend digest to ef73e19 Jul 12, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch from 983c7f5 to 1a5c3d7 Compare July 12, 2025 02:56
@renovate renovate bot changed the title Update github.com/diggerhq/digger/backend digest to ef73e19 Update github.com/diggerhq/digger/backend digest to 1bfb31d Jul 12, 2025
@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch 2 times, most recently from b0a9773 to c632442 Compare July 18, 2025 01:38
Copy link
Contributor Author

renovate bot commented Jul 18, 2025

⚠️ 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-20250718034728-fd83543ef8b7
go: downloading github.com/slack-go/slack v0.10.3
go: downloading github.com/robfig/cron/v3 v3.0.1
go: downloading github.com/gorilla/websocket v1.5.0
go: downloading gorm.io/datatypes v1.1.1-0.20230130040222-c43177d3cf8c
go: downloading github.com/diggerhq/digger v0.6.109
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/[email protected]: 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

@renovate renovate bot changed the title Update github.com/diggerhq/digger/backend digest to 1bfb31d Update github.com/diggerhq/digger/backend digest to e42e965 Jul 18, 2025
Copy link
Contributor

bismuthdev bot commented Jul 18, 2025

Bismuth completed its review and found no issues.

@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch from c632442 to 320c975 Compare July 18, 2025 03:37
@renovate renovate bot changed the title Update github.com/diggerhq/digger/backend digest to e42e965 Update github.com/diggerhq/digger/backend digest to de6a760 Jul 18, 2025
Copy link
Contributor

bismuthdev bot commented Jul 18, 2025

Bismuth completed its review and found no issues.

@renovate renovate bot force-pushed the renovate/github.com-diggerhq-digger-backend-digest branch from 320c975 to 21d352f Compare July 18, 2025 06:17
@renovate renovate bot changed the title Update github.com/diggerhq/digger/backend digest to de6a760 Update github.com/diggerhq/digger/backend digest to fd83543 Jul 18, 2025
Copy link
Contributor

bismuthdev bot commented Jul 18, 2025

Summary of Bugs Found

Total bugs found: 4

Critical Issues:

  1. Future Go Version Specification - In ee/drift/go.mod, Go version was incorrectly set to 1.24.0, which is a future/non-standard version that would cause build failures on systems with current Go versions.

  2. Future Dependency Timestamps - Found in three different files:

    • ee/backend/go.mod
    • ee/cli/go.mod
    • next/go.mod

    All three files contained dependencies with timestamps from July 2025 (v0.0.0-20250718034728-fd83543ef8b7), likely a typo for 2024. These future timestamps can cause dependency resolution problems across the codebase.

@@ -10,7 +10,7 @@ require (
github.com/bradleyfalzon/ghinstallation/v2 v2.11.0
github.com/buildkite/go-buildkite/v3 v3.11.0
github.com/dchest/uniuri v1.2.0
github.com/diggerhq/digger/backend v0.0.0-20241111113338-9a40639ab83c
github.com/diggerhq/digger/backend v0.0.0-20250718034728-fd83543ef8b7
Copy link
Contributor

Choose a reason for hiding this comment

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

The backend dependency in ee/backend/go.mod has a timestamp in the future (July 2025) which could cause issues with dependency resolution. The version string v0.0.0-20250718034728-fd83543ef8b7 contains a date component that is set to 2025-07-18, which is in the future. This is likely a typo where 2025 was written instead of 2024.

Go modules use these pseudo-version timestamps for version ordering, and having a future timestamp could cause problems with dependency resolution, especially when other tools or systems try to validate the timestamp. The same future timestamp appears in multiple files (ee/cli/go.mod and next/go.mod), indicating this is a systematic issue across the codebase.

Suggested change
github.com/diggerhq/digger/backend v0.0.0-20250718034728-fd83543ef8b7
github.com/diggerhq/digger/backend v0.0.0-20240718034728-fd83543ef8b7

@@ -7,7 +7,7 @@ replace github.com/diggerhq/digger/libs => ../../libs
replace github.com/diggerhq/digger/cli => ../../cli

require (
github.com/diggerhq/digger/backend v0.0.0-20241111113338-9a40639ab83c
github.com/diggerhq/digger/backend v0.0.0-20250718034728-fd83543ef8b7
Copy link
Contributor

Choose a reason for hiding this comment

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

The backend dependency in ee/cli/go.mod has a timestamp in the future (July 2025) which could cause issues with dependency resolution. The version string v0.0.0-20250718034728-fd83543ef8b7 contains a date component that is set to 2025-07-18, which is in the future. This is likely a typo where 2025 was written instead of 2024.

Go modules use these pseudo-version timestamps for version ordering, and having a future timestamp could cause problems with dependency resolution, especially when other tools or systems try to validate the timestamp.

Suggested change
github.com/diggerhq/digger/backend v0.0.0-20250718034728-fd83543ef8b7
github.com/diggerhq/digger/backend v0.0.0-20240718034728-fd83543ef8b7

@@ -9,7 +9,7 @@ replace github.com/diggerhq/digger/libs => ../libs
require (
github.com/bradleyfalzon/ghinstallation/v2 v2.11.0
github.com/dchest/uniuri v1.2.0
github.com/diggerhq/digger/backend v0.0.0-20241111113338-9a40639ab83c
github.com/diggerhq/digger/backend v0.0.0-20250718034728-fd83543ef8b7
Copy link
Contributor

Choose a reason for hiding this comment

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

The backend dependency in next/go.mod has a timestamp in the future (July 2025) which could cause issues with dependency resolution. The version string v0.0.0-20250718034728-fd83543ef8b7 contains a date component that is set to 2025-07-18, which is in the future. This is likely a typo where 2025 was written instead of 2024.

Go modules use these pseudo-version timestamps for version ordering, and having a future timestamp could cause problems with dependency resolution, especially when other tools or systems try to validate the timestamp.

Suggested change
github.com/diggerhq/digger/backend v0.0.0-20250718034728-fd83543ef8b7
github.com/diggerhq/digger/backend v0.0.0-20240718034728-fd83543ef8b7

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