Repository navigation
[Backport release-1.6] fix(e2e-sandbox): install mc from its GitHub release - #4535
Conversation
dl.min.io now answers 410 Gone for every community mc build, since MinIO archived the project, so the sandbox image no longer builds. The final mc release is still published as a GitHub release asset. Pin it and verify the per-arch checksum, because the old install trusted whatever the URL served. Assisted-by: LLM Signed-off-by: Aleksei Sviridkin <[email protected]> (cherry picked from commit e66f134) Signed-off-by: Myasnikov Daniil <[email protected]>
github-actions
Bot
added
size/S
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: cozystack/cozystack/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
3 participants
What this PR does
Backports the mc download fix from the dependency rollup to
release-1.6. Only the mc commit is cherry-picked, with its original author and-xreference.The release-line build fails because
dl.min.ioreturns HTTP 410. This is the same problem as the closed mc download issue, whose fix had only reachedmain.Validation: the local amd64 image builds and
mc --versionworks inside it. Downloads, SHA256 and ELF architecture checks passed for amd64 and arm64, and the install command rejects corrupted downloads and unsupported architectures. The fullmake unit-teststarget passed.Screenshots
No UI changes.
Downstream repositories
Release note