This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/go_modules/golang.org/x/sync-0.7.0
in repository https://gitbox.apache.org/repos/asf/camel-k.git
omit 4b9ccaa3d chore(deps): bump golang.org/x/sync from 0.6.0 to 0.7.0
add 0f439b368 chore(helm): release 2.3.0
add 61658be64 chore: bump next version to 2.4.0-SNAPSHOT
add fc6e8d4b5 chore(deps): bump golang.org/x/sync from 0.6.0 to 0.7.0
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch 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 (4b9ccaa3d)
\
N -- N -- N
refs/heads/dependabot/go_modules/golang.org/x/sync-0.7.0 (fc6e8d4b5)
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.
No new revisions were added by this update.
Summary of changes:
docs/charts/camel-k-2.3.0.tgz | Bin 0 -> 273905 bytes
docs/charts/index.yaml | 99 +++++++++++++--------
helm/camel-k/Chart.yaml | 2 +-
helm/camel-k/values.yaml | 2 +-
java/crds/pom.xml | 2 +-
java/maven-logging/pom.xml | 2 +-
.../config/manager/operator-deployment.yaml | 6 +-
.../bases/camel-k.clusterserviceversion.yaml | 10 +--
pkg/resources/config/manifests/kustomization.yaml | 2 +-
pkg/util/defaults/defaults.go | 2 +-
script/Makefile | 4 +-
11 files changed, 79 insertions(+), 52 deletions(-)
create mode 100644 docs/charts/camel-k-2.3.0.tgz
