-
Notifications
You must be signed in to change notification settings - Fork 562
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
base: develop
Are you sure you want to change the base?
Conversation
ℹ Artifact update noticeFile name: ee/drift/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this 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 inee/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
1fde5c5
to
b62e994
Compare
b62e994
to
647cf89
Compare
647cf89
to
278ad45
Compare
278ad45
to
b311a26
Compare
b311a26
to
d56d45b
Compare
693143c
to
c567f42
Compare
c567f42
to
6451b4f
Compare
ba4fa90
to
b3b50a4
Compare
b3b50a4
to
4177c0c
Compare
4177c0c
to
2c5993b
Compare
2c5993b
to
c58a454
Compare
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 |
There was a problem hiding this comment.
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.
github.com/diggerhq/digger/next cc703a9dc0c3 | |
github.com/diggerhq/digger/next v0.0.0-20240724000000-cc703a9dc0c3 |
5ab7a4d
to
e781746
Compare
Bug SummaryTotal Bugs Found: 1 Critical Bug
|
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 |
There was a problem hiding this comment.
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:
- A semantic version (like
v1.2.3
) - 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.
github.com/diggerhq/digger/next 71e3c0a3f4ca | |
github.com/diggerhq/digger/next v0.0.0-20240724000000-71e3c0a3f4ca |
e781746
to
2421561
Compare
Bug SummaryTotal Bugs Found: 1Bug Summary:
|
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 |
There was a problem hiding this comment.
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 prefix20240724000000
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.
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 |
There was a problem hiding this comment.
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.
github.com/diggerhq/digger/next c4be2e37ed23 | |
github.com/diggerhq/digger/next v0.0.0-20240724000000-c4be2e37ed23 |
2421561
to
686168a
Compare
Bug SummaryTotal Bugs Found: 1 Bug Details
|
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 |
There was a problem hiding this comment.
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.
github.com/diggerhq/digger/next e8a86a2223cc | |
github.com/diggerhq/digger/next v0.0.0-20240725000000-e8a86a2223cc |
686168a
to
efb67df
Compare
Bug SummaryTotal bugs found: 1 Critical Bug Details
|
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 |
There was a problem hiding this comment.
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 prefix20240725000000
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.
github.com/diggerhq/digger/next 2678e7585667 | |
github.com/diggerhq/digger/next v0.0.0-20240725000000-2678e7585667 |
efb67df
to
7a103f7
Compare
Bug SummaryTotal Bugs Found: 1 Bug Details
|
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 |
There was a problem hiding this comment.
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 prefix20240705
is the date in YYYYMMDD format05d0425d52e2
is the commit hash
This follows Go's pseudo-version format for commit-based dependencies.
github.com/diggerhq/digger/next 05d0425d52e2 | |
github.com/diggerhq/digger/next v0.0.0-20240705-05d0425d52e2 |
7a103f7
to
73308c0
Compare
Bug SummaryTotal Bugs Found: 1 Critical Bug
|
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 |
There was a problem hiding this comment.
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-versions20240725
would be the date of the commit (or another appropriate date)043926
is the timestamp portion043926b20e16
is the commit hash
This invalid format will cause build failures when trying to resolve dependencies.
github.com/diggerhq/digger/next 043926b20e16 | |
github.com/diggerhq/digger/next v0.0.0-20240725043926-043926b20e16 |
73308c0
to
f5d423f
Compare
Bismuth completed its review and found no issues. |
This PR contains the following updates:
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.
This PR was generated by Mend Renovate. View the repository job log.