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 463afc386 (commit)
to 7c7777e0d (commit)
discard 463afc386 chore(ci): v2.11.0-nightly release updates
add c3a5a18f4 chore(ci): run bundle with install-mode option
add dd4ef9493 chore(e2e): remove clients update
add 07ef9d715 chore(deps): bump github.com/sirupsen/logrus from 1.10.0 to
1.10.1
add 214ddf1d5 fix(ci): proper impots
new 7c7777e0d 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 (463afc386)
\
N -- N -- N refs/tags/v2.11.0-nightly (7c7777e0d)
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 281787 -> 281782 bytes
docs/charts/index.yaml | 6 +-
e2e/common/misc/scale_integration_test.go | 70 ----
e2e/install/olm/olm_install_test.go | 422 ++++++++++-----------
go.mod | 2 +-
go.sum | 4 +-
.../bases/camel-k.clusterserviceversion.yaml | 2 +-
script/Makefile | 2 +-
8 files changed, 217 insertions(+), 291 deletions(-)
