Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 5.0.12 #1974

Merged
merged 1 commit into from
Feb 6, 2024
Merged

Release 5.0.12 #1974

merged 1 commit into from
Feb 6, 2024

Conversation

pjuarezd
Copy link
Member

@pjuarezd pjuarezd commented Feb 6, 2024

No description provided.

Signed-off-by: pjuarezd <pjuarezd@users.noreply.github.com>
@pjuarezd pjuarezd merged commit e043e1b into minio:master Feb 6, 2024
26 checks passed
@pjuarezd pjuarezd deleted the release-5.0.12 branch February 6, 2024 21:06
@jplimack
Copy link

jplimack commented Feb 7, 2024

@pjuarezd @cniackz @reivaj05 there is no v5.0.12 in the quay.io registry, so this broke consumers of the helm chart

 crane ls quay.io/minio/operator | grep v5.0.1  
v5.0.1-amd64
v5.0.1-ppc64le
v5.0.1-s390x
v5.0.1-arm64
v5.0.1
v5.0.10-amd64
v5.0.10-ppc64le
v5.0.10-s390x
v5.0.10-arm64
v5.0.10
v5.0.11-amd64
v5.0.11-arm64
v5.0.11-s390x
v5.0.11-ppc64le
v5.0.11

@jplimack
Copy link

jplimack commented Feb 7, 2024

theres also no release for v5.0.12
https://github.com/minio/operator/releases

@cesnietor
Copy link
Contributor

release is still in progress @jplimack, we'll make the release soon.

@jplimack
Copy link

jplimack commented Feb 7, 2024

is it possible to keep the version set in the helm file matching the latest release via a github action? this mismatch is a bit painful for downstream consumers. its also not obvious why this release isnt actually released

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants