fix(github-release): update dragonflydb/dragonfly-operator ( v1.1.7 → v1.1.8 ) #556
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.
This PR contains the following updates:
v1.1.7
->v1.1.8
Release Notes
dragonflydb/dragonfly-operator (dragonflydb/dragonfly-operator)
v1.1.8
Compare Source
Release
v1.1.8
Docker image:
docker.dragonflydb.io/dragonflydb/operator:v1.1.8
Helm chart:
oci://ghcr.io/dragonflydb/dragonfly-operator/helm:v1.1.8
This release bumps the Dragonfly version to
v1.124.0
, and has some other improvements around Memcached, ImagePullPolicy, etcWhat's Changed
New Contributors
Full Changelog: dragonflydb/dragonfly-operator@v1.1.7...v1.1.8
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 this update again.
This PR was generated by Mend Renovate. View the repository job log.