wenjin272 opened a new pull request, #1288:
URL: https://github.com/apache/flink-agents/pull/1288

   Linked issue: none (hotfix)
   
   ### Purpose of change
   
   Restore Milvus setup in release-0.3 CI, which currently fails to pull 
`minio/minio:RELEASE.2023-03-20T20-16-18Z` before the cross-language tests can 
run. See the [failure on 
#1286](https://github.com/apache/flink-agents/actions/runs/39361720470/job/118429197623).
   
   Cherry-pick #1162 (`404d5b6efeafc9f2574b35c1a12428bd3af52605`) from main. 
Use `bitnamilegacy/minio:2025.7.23` with its root-credential variables, default 
entrypoint, data directory, and bash-based health check. The registry-line 
conflict was resolved to the final main-branch configuration; the resulting 
Compose file is identical to the source commit. Original authorship is 
preserved.
   
   ### Tests
   
   - `docker compose -f tools/docker/milvus/docker-compose.yml config --quiet`: 
passed.
   - `docker compose -f tools/docker/milvus/docker-compose.yml config 
--images`: selects the replacement MinIO image.
   - `docker manifest inspect bitnamilegacy/minio:2025.7.23`: succeeded; Linux 
amd64 and arm64 manifests are available.
   - `git diff --check`: passed; verified the Compose file matches the source 
commit exactly.
   - Container startup and cross-language tests were not run locally because 
the Docker daemon is not running. Validation of service startup and integration 
behavior is left to this PR's CI.
   
   ### API
   
   No public API changes.
   
   ### Documentation
   
   - [ ] `doc-needed`
   - [x] `doc-not-needed`
   - [ ] `doc-included`
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   - [x] Yes
   - [ ] No
   
   Generated-by: Codex CLI 0.153.4 (GPT-6)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to