Update github.com/diggerhq/digger/backend digest to 1d8067a

renovate[bot] commented 2 weeks ago

This PR contains the following updates:

Package	Type	Update	Change
github.com/diggerhq/digger/backend	require	digest	`9a40639` -> `1d8067a`
github.com/diggerhq/digger/backend	require	digest	`90aa7b8` -> `1d8067a`

[!WARNING] Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

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.

delve-auditor[bot] commented 2 weeks ago

✅ No security or compliance issues detected. Reviewed everything up to bdbcedc55e5aee99d3066f239d1ca58e2262e0be.

Security Overview

- 🔎 **Scanned files:** 8 changed file(s)

Detected Code Changes

| Change Type | Relevant files | |------------|----------------| | Enhancement | ► go.mod
Update digger/backend dependency to 1d8067a
► go.sum
Update dependency checksums |

Reply to this PR with @delve-auditor followed by a description of what change you want and we'll auto-submit a change to this PR to implement it.

renovate[bot] commented 2 weeks ago

ℹ Artifact update notice

File name: ee/backend/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/samber/lo`	`v1.39.0` -> `v1.46.0`
`github.com/bytedance/sonic`	`v1.11.6` -> `v1.11.9`
`github.com/gabriel-vasile/mimetype`	`v1.4.3` -> `v1.4.4`
`github.com/getsentry/sentry-go`	`v0.28.0` -> `v0.29.0`
`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`

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

28 additional dependencies were updated

Details:

Package	Change
`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/jackc/pgservicefile`	`v0.0.0-20221227161230-091c0ba34f0a` -> `v0.0.0-20231201235250-de7065d80cb9`
`github.com/jackc/pgx/v5`	`v5.4.3` -> `v5.5.5`
`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):

27 additional dependencies were updated

Details:

Package	Change
`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/go-sql-driver/mysql`	`v1.7.0` -> `v1.8.1`
`github.com/jackc/pgservicefile`	`v0.0.0-20221227161230-091c0ba34f0a` -> `v0.0.0-20231201235250-de7065d80cb9`
`gorm.io/datatypes`	`v1.1.1-0.20230130040222-c43177d3cf8c` -> `v1.2.4`

File name: next/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):

27 additional dependencies were updated

Details:

Package	Change
`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/go-sql-driver/mysql`	`v1.7.0` -> `v1.8.1`
`github.com/jackc/pgservicefile`	`v0.0.0-20221227161230-091c0ba34f0a` -> `v0.0.0-20231201235250-de7065d80cb9`
`gorm.io/datatypes`	`v1.1.1-0.20230130040222-c43177d3cf8c` -> `v1.2.4`

coderabbitai[bot] commented 1 day ago

[!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](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

diggerhq / digger