Combine Dependabot PRs #11983
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -18,6 +18,6 @@ jobs: | |
| if: github.repository == 'testcontainers/testcontainers-java' | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: release-drafter/release-drafter@eada3c96a64734dd381cfbda23511034e328ddb0 # v5.19.0 | ||
|
There was a problem hiding this comment. 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win 🔎 Supported by static analysis🏁 Script executed: #!/bin/bash
set -u
printf '%s\n' '--- workflow line ---'
nl -ba .github/workflows/release-drafter.yml | sed -n '17,24p'
resolve_tag() {
local tag="$1"
local ref_json object_type object_sha commit_sha
ref_json="$(curl -fsSL "https://api.github.com/repos/release-drafter/release-drafter/git/ref/tags/${tag}")"
object_type="$(printf '%s' "$ref_json" | jq -r '.object.type')"
object_sha="$(printf '%s' "$ref_json" | jq -r '.object.sha')"
if [ "$object_type" = "tag" ]; then
commit_sha="$(curl -fsSL "https://api.github.com/repos/release-drafter/release-drafter/git/tags/${object_sha}" | jq -r '.object.sha')"
else
commit_sha="$object_sha"
fi
printf '%s type=%s ref_object=%s commit=%s\n' "$tag" "$object_type" "$object_sha" "$commit_sha"
curl -fsSL "https://api.github.com/repos/release-drafter/release-drafter/commits/${commit_sha}" | jq -r '"validated_commit="+.sha'
}
resolve_tag v7.6.0
resolve_tag v5.19.0
resolve_tag v6.1.0
printf '%s\n' '--- pinned commit validation ---'
curl -fsSL 'https://api.github.com/repos/release-drafter/release-drafter/commits/eada3c96a64734dd381cfbda23511034e328ddb0' \
| jq -r '"validated_pin="+.sha'Repository: testcontainers/testcontainers-java Length of output: 841 🌐 Web query:
💡 Result: The GitHub commit eada3c96a64734dd381cfbda23511034e328ddb0 corresponds to release v7.6.0 of the release-drafter/release-drafter repository [1][2]. This version was published on July 19, 2026 [1][3]. Key highlights of the v7.6.0 release include: New Features: - Ability to resolve release commitish references to specific commits [1]. - Inclusion of a new contributors list [1]. - Support for pull request co-authors [1]. - Support for per-key merge strategies within _extends [1]. Bug Fixes: - Correction for.github in legacy _extends references [1]. - Normalization of release target branch references [1]. - Resolution of issues with duplicate and skipped release contributors [1]. Maintenance and dependency updates were also included, such as updates to graphql, yaml, semver, ignore, and Citations:
🏁 Script executed: #!/bin/bash
set -u
for endpoint in \
'https://api.github.com/repos/release-drafter/release-drafter/git/ref/tags/v7.6.0' \
'https://api.github.com/repos/release-drafter/release-drafter/git/ref/tags/v6.1.0' \
'https://api.github.com/repos/release-drafter/release-drafter/commits/eada3c96a64734dd381cfbda23511034e328ddb0'
do
echo "--- $endpoint"
curl -fsSL "$endpoint" | jq '{sha: (.object.sha // .sha), type: .object.type, message: (.commit.message // null)}'
doneRepository: testcontainers/testcontainers-java Length of output: 750 Correct the pinned release comment. The pinned commit resolves to Release Drafter 🤖 Prompt for AI Agents |
||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,5 +3,5 @@ description = "Testcontainers :: Milvus" | |
| dependencies { | ||
| api project(':testcontainers') | ||
|
|
||
| testImplementation 'io.milvus:milvus-sdk-java:3.0.3' | ||
|
There was a problem hiding this comment. 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win 🔎 Supported by static analysis🏁 Script executed: #!/bin/bash
printf '%s\n' '--- modules/milvus/build.gradle ---'
cat -n modules/milvus/build.gradle
printf '%s\n' '--- MilvusContainerTest.java ---'
cat -n modules/milvus/src/test/java/org/testcontainers/milvus/MilvusContainerTest.java
printf '%s\n' '--- nearby Milvus module references ---'
rg -n --glob '!build/**' --glob '!node_modules/**' 'milvus-sdk-java|milvusdb/milvus|MilvusContainer|v2\.3\.9|3\.0\.3' modules/milvusRepository: testcontainers/testcontainers-java Length of output: 5057 🌐 Web query:
💡 Result: The Milvus Java SDK version 3.0.3 is not compatible with the Milvus server version 2.3.9 [1][2]. According to the official Milvus compatibility documentation, the Java SDK and Milvus server versions have specific recommended pairings [1][2]. For Milvus server version 2.3.x, the recommended Java SDK version is typically in the 2.3.x range (specifically, version 2.3.9 is explicitly listed as recommended for Milvus 2.3.x in the official documentation) [2]. Conversely, Java SDK version 3.0.3 is designed for and compatible with Milvus server version 3.0.x [1][3]. Using a 3.x SDK with a 2.3.x server is generally not supported due to significant architectural changes and API updates introduced in Milvus 3.0 [4]. You should use a Java SDK version from the 2.3.x release series to ensure compatibility with your Milvus 2.3.9 server [2][5]. Citations:
Align the Milvus SDK with the test server.
🤖 Prompt for AI Agents |
||
| } | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,7 +3,7 @@ description = "Testcontainers :: Qdrant" | |
| dependencies { | ||
| api project(':testcontainers') | ||
|
|
||
| testImplementation 'io.qdrant:client:1.18.3' | ||
|
There was a problem hiding this comment. 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win 🔎 Supported by static analysis🏁 Script executed: #!/bin/bash
printf '%s\n' '--- modules/qdrant/build.gradle ---'
cat -n modules/qdrant/build.gradle
printf '%s\n' '--- QdrantContainerTest.java ---'
cat -n modules/qdrant/src/test/java/org/testcontainers/qdrant/QdrantContainerTest.java
printf '%s\n' '--- relevant repository references ---'
rg -n --glob '!*build*' --glob '!node_modules' 'io\.qdrant:client|qdrant/qdrant|1\.7\.4|1\.18\.3|QdrantContainer' modules/qdrantRepository: testcontainers/testcontainers-java Length of output: 6735 🌐 Web query:
💡 Result: Qdrant client 1.18.3 is not compatible with Qdrant server 1.7.4. According to Qdrant's official compatibility policy, the client and server must have matching major versions, and their minor versions must not differ by more than one [1][2][3][4]. Specifically, the Qdrant SDK and server compatibility rules are as follows: - Major versions must match [5][3]. - The difference between minor versions must not exceed 1 [2][3][4]. - Qdrant client 1.18.x and server 1.18.x are considered compatible [5]. Using a client from the 1.18.x series requires a server version of at least 1.17.x [2][4]. Because the client is version 1.18.x and the server is 1.7.x, the minor version difference is 11, which significantly exceeds the allowed limit of 1 [2][3][4]. The Qdrant client performs an automatic version check during initialization, which will generate a compatibility warning or error when it detects this discrepancy [3][6]. To ensure proper functionality, it is recommended to upgrade your Qdrant server to a version within the 1.17.x or 1.18.x series [1][7][8]. If you must maintain an older server, you should use a client version that is within one minor version of your server (e.g., a client from the 1.6.x, 1.7.x, or 1.8.x series) [2][3][4]. Citations:
🌐 Web query:
💡 Result: The Qdrant Java client version 1.18.3 is primarily designed for compatibility with Qdrant server version 1.18.x [1][2]. By default, the Qdrant Java client performs a version compatibility check during initialization [3]. According to the client's design, compatible versions are generally those that differ by at most one minor version (e.g., a 1.6.x client is considered compatible with 1.5.x and 1.7.x server versions) [3]. However, for optimal performance and to ensure full support for all API features, using a client version that matches the server's major and minor version is recommended [1][2]. If you encounter compatibility warnings, you have the option to disable the automatic version check by adjusting the client initialization parameters [3]. Citations:
Align the Qdrant client and test image versions.
🤖 Prompt for AI Agents |
||
| testImplementation platform('io.grpc:grpc-bom:1.80.0') | ||
| testImplementation 'io.grpc:grpc-stub' | ||
| testImplementation 'io.grpc:grpc-protobuf' | ||
|
|
||
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.
🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: testcontainers/testcontainers-java
Length of output: 2095
🌐 Web query:
Official Slack GitHub Action v4 incoming webhook configuration: determine whetherwebhook,webhook-type: incoming-webhook, andSLACK_WEBHOOK_URLare required or supported.💡 Result:
In the Slack GitHub Action v4, the configuration parameters
webhook,webhook-type, and the environment variableSLACK_WEBHOOK_URLare used together to facilitate sending messages via incoming webhooks [1][2]. 1. SLACK_WEBHOOK_URL: This is the recommended name for the repository secret used to store your Slack incoming webhook URL [1][2]. While you can use any name for your secret, this is the standard naming convention used in the official documentation [1][2]. 2. webhook: This input parameter is required to specify the destination URL for your request [1][2]. In standard configurations, this is typically set to the value of your stored secret:${{ secrets.SLACK_WEBHOOK_URL }}[1][2]. 3. webhook-type: This input parameter is required to define the behavior of the action [1][2][3]. When sending messages to an incoming webhook URL, you must explicitly set this toincoming-webhook[1][2]. When configuring the action, provide these as follows [1][2]: - name: Post a message in a channel uses: slackapi/slack-github-action@v4.0.0 with: webhook: ${{ secrets.SLACK_WEBHOOK_URL }} webhook-type: incoming-webhook payload: | text: "Your message here" Thewebhook-typeparameter is critical; if it is incorrectly set (e.g., towebhook-trigger), the action may behave unexpectedly, such as triggering retries or failing to format the message correctly for an incoming webhook endpoint [3][4].Citations:
webhook-type: webhook-triggerstep delivers duplicate messages, then hangs until the job timeout slackapi/slack-github-action#654Configure the Slack incoming webhook for v4.
Slack GitHub Action v4 requires
webhookandwebhook-type: incoming-webhookfor incoming webhook requests. ReplaceSLACK_WEBHOOK_URLwith thewebhookinput and add the webhook type so failure notifications can post.🧰 Tools
🪛 zizmor (1.29.0)
[warning] 19-65: overly broad permissions (excessive-permissions): default permissions used due to no permissions: block
(excessive-permissions)
🤖 Prompt for AI Agents