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

⬆(group): rook-ceph ( v1.16.3 → v1.16.4 ) (patch) #1484

Merged
merged 1 commit into from
Feb 21, 2025

Conversation

shamubot[bot]
Copy link
Contributor

@shamubot shamubot bot commented Feb 20, 2025

This PR contains the following updates:

Package Update Change
rook-ceph patch v1.16.3 -> v1.16.4
rook-ceph-cluster patch v1.16.3 -> v1.16.4

Release Notes

rook/rook (rook-ceph)

v1.16.4

Compare Source

Improvements

Rook v1.16.4 is a patch release limited in scope and focusing on feature additions and bug fixes to the Ceph operator.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

Copy link

trunk-io bot commented Feb 20, 2025

⏱️ 57s total CI duration on this PR

Job Cumulative Duration Recent Runs
Trunk Check Runner 21s 🟩
Flux Helm Repository Sync 21s 🟩
Flux Diff (kubernetes, helmrelease) 11s 🟩
Label Size 2s 🟩
Labeler 2s 🟩

settingsfeedbackdocs ⋅ learn more about trunk.io

@shamubot
Copy link
Contributor Author

shamubot bot commented Feb 20, 2025

no HelmRelease objects found in cluster

@kiliantyler kiliantyler merged commit 24ad0b4 into main Feb 21, 2025
7 checks passed
@kiliantyler kiliantyler deleted the shamubot/patch-rook-ceph branch February 21, 2025 01:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant