chore(deps): update dependency operator-framework/operator-registry to v1.62.0 #475
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:
1.23.0→1.62.0Release Notes
operator-framework/operator-registry (operator-framework/operator-registry)
v1.62.0Compare Source
What's Changed
Full Changelog: operator-framework/operator-registry@v1.61.0...v1.62.0
v1.61.0Compare Source
What's Changed
New Contributors
Full Changelog: operator-framework/operator-registry@v1.60.0...v1.61.0
v1.60.0Compare Source
Notice
This release bumps k8s to 1.34
What's Changed
New Contributors
Full Changelog: operator-framework/operator-registry@v1.59.0...v1.60.0
v1.59.0Compare Source
What's Changed
Full Changelog: operator-framework/operator-registry@v1.58.0...v1.59.0
v1.58.0Compare Source
Potential breaking changes
opm validatewhich includes the ability to validate that no included bundle versions are stranded, since without validation it's relatively easy to create edges which OLM ignores when evaluating potential upgrades. Capabilities added toopm alpha render-graphin #1744 attempt to make this more apparent to operator authors.What's Changed
Full Changelog: operator-framework/operator-registry@v1.57.0...v1.58.0
v1.57.0Compare Source
What's Changed
New Contributors
Full Changelog: operator-framework/operator-registry@v1.56.0...v1.57.0
v1.56.0Compare Source
What's Changed
New Contributors
Full Changelog: operator-framework/operator-registry@v1.55.0...v1.56.0
v1.55.0Compare Source
What's Changed
Operators can now include NetworkPolicy resources in their manifests. This enhancement enables more granular control over network security policies within Kubernetes clusters, improving isolation and control over network traffic between pods: PR #1675 by @rashmigottipati.
Full Changelog: operator-framework/operator-registry@v1.54.0...v1.55.0
v1.54.0Compare Source
What's Changed
Full Changelog: operator-framework/operator-registry@v1.53.0...v1.54.0
v1.53.0Compare Source
Possible Breaking Changes
Non-Breaking Changes
What's Changed
Full Changelog: operator-framework/operator-registry@v1.52.0...v1.53.0
v1.52.0Compare Source
What's Changed
New Contributors
Full Changelog: operator-framework/operator-registry@v1.51.0...v1.52.0
v1.51.0Compare Source
Possible Breaking Changes
opmby including only user (o600) permissions to align with security best practices. This impactsopm migrateoutput (for example).What's Changed
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.