This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to tag v2.11.0-nightly
in repository https://gitbox.apache.org/repos/asf/camel-k.git
*** WARNING: tag v2.11.0-nightly was modified! ***
from f20759930 (commit)
to 024a43091 (commit)
discard f20759930 chore(ci): v2.11.0-nightly release updates
add 44d334b45 chore(e2e): increase timeouts
add 9e9b6b100 fix(e2e): affinity it names regression
add 1c980893d fix(cmd): read operator image from Pod
add 2c8b9e0be chore: nightly automatic updates
new 024a43091 chore(ci): v2.11.0-nightly release updates
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
tag are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (f20759930)
\
N -- N -- N refs/tags/v2.11.0-nightly (024a43091)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
docs/charts/camel-k-2.11.0-nightly.tgz | Bin 282553 -> 282551 bytes
docs/charts/index.yaml | 6 +-
e2e/common/traits/affinity_test.go | 26 +++---
pkg/cmd/operator/operator.go | 40 +++++++++-
pkg/cmd/operator/operator_test.go | 87 +++++++++++++++++++--
pkg/resources/config/manager/kustomization.yaml | 10 ---
.../config/manager/operator-deployment.yaml | 3 -
.../bases/camel-k.clusterserviceversion.yaml | 2 +-
script/Makefile | 2 +-
9 files changed, 136 insertions(+), 40 deletions(-)
