Conversation
MinIO archived the open-source Server, Client (mc) and KES projects and stopped serving their binaries: every artifact under dl.min.io now returns HTTP 410 Gone. The "Setup MinIO" step fails on the first download with curl exit 22, so the Yezzey CI Pipeline has been red on REL_2_STABLE for all five matrix OSes since 2026-09-11. Pin the final open-source releases from their GitHub release assets, which are still published, and verify each binary against the sha256sum MinIO publishes next to it. The previous code piped an unverified binary straight to /usr/local/bin. Server RELEASE.2025-09-07T16-13-09Z, client RELEASE.2025-08-13T08-35-41Z. Both keep the minio/mc file names, so the rest of the step -- starting the server, the health probe and the bucket setup -- is unchanged. The release/checksum values are plain shell variables rather than job-level env: anything exported with a MINIO_ prefix would be picked up by the MinIO server as configuration.
leborchuk
approved these changes
Sep 14, 2026
leborchuk
left a comment
leborchuk
left a comment
Contributor
There was a problem hiding this comment.
LGTM, we could switch from minio to seaweedfs but lot more work is needed for that. Let's use github binaries
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
MinIO archived the open-source Server, Client (mc) and KES projects and stopped serving their binaries: every artifact under dl.min.io now returns HTTP 410 Gone. The "Setup MinIO" step fails on the first download with curl exit 22, so the Yezzey CI Pipeline has been red on REL_2_STABLE for all five matrix OSes since 2026-09-11.
Pin the final open-source releases from their GitHub release assets, which are still published, and verify each binary against the sha256sum MinIO publishes next to it. The previous code piped an unverified binary straight to /usr/local/bin.
Server RELEASE.2025-09-07T16-13-09Z, client RELEASE.2025-08-13T08-35-41Z. Both keep the minio/mc file names, so the rest of the step -- starting the server, the health probe and the bucket setup -- is unchanged.
The release/checksum values are plain shell variables rather than job-level env: anything exported with a MINIO_ prefix would be picked up by the MinIO server as configuration.
Fixes #ISSUE_Number
What does this PR do?
Type of Change
Breaking Changes
Test Plan
make installcheckmake -C src/test installcheck-cbdb-parallelImpact
Performance:
User-facing changes:
Dependencies:
Checklist
Additional Context
CI Skip Instructions