This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to tag v2.10.0-nightly
in repository https://gitbox.apache.org/repos/asf/camel-k.git
*** WARNING: tag v2.10.0-nightly was modified! ***
from a3d80cafb (commit)
to f8950636a (commit)
discard a3d80cafb chore(ci): v2.10.0-nightly release updates
add b2ceac8f1 fix: support operator sharding in Camel K Helm chart with
custom release names in cluster-wide scope
add fb43d26f7 chore(deps): bump knative.dev/serving from 0.48.1 to 0.48.2
add b95184d05 chore: nightly automatic updates
new f8950636a chore(ci): v2.10.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 (a3d80cafb)
\
N -- N -- N refs/tags/v2.10.0-nightly (f8950636a)
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.10.0-nightly.tgz | Bin 280109 -> 280124 bytes
docs/charts/index.yaml | 6 +++---
go.mod | 4 ++--
go.sum | 8 ++++----
helm/camel-k/templates/operator-deployment.yaml | 8 ++++----
helm/camel-k/templates/operator-svcs.yaml | 4 ++--
.../bases/camel-k.clusterserviceversion.yaml | 2 +-
7 files changed, 16 insertions(+), 16 deletions(-)
