[datadog-operator] Release v1.29.0-rc.1#3239
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c555b7b846
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| features.operators.openshift.io/token-auth-azure: "false" | ||
| features.operators.openshift.io/token-auth-gcp: "false" | ||
| olm.skipRange: '>=1.7.0 <1.28.0' | ||
| olm.skipRange: '>=1.7.0 <1.29.0-rc.1' |
There was a problem hiding this comment.
Because this CSV is for 1.29.0-rc.1 and the bundle metadata still puts it in the default stable channel, this skipRange makes every installed stable version >=1.7.0 and <1.29.0-rc.1 eligible to upgrade to the release candidate; the main bundle also directly replaces 1.28.0. If this bundle is published to the normal OperatorHub/Red Hat catalogs, stable subscribers can be offered the RC instead of waiting for 1.29.0, so prerelease bundles should use a separate RC channel or avoid adding stable-channel update edges.
Useful? React with 👍 / 👎.
|
gh-worker-dd-devflow-36fce6
Bot
added
mergequeue-status: queued
mergequeue-status: in_progress
and removed
mergequeue-status: queued
labels
58d8ffb
into
v1.29
1 participant
No description provided.