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/term-0.23.0
in repository https://gitbox.apache.org/repos/asf/camel-k.git
discard 5d2c6d539 chore(deps): bump golang.org/x/term from 0.22.0 to 0.23.0
add 53f500ee4 chore(ci): 2.4.0 helm release
add 9c237b775 chore(release): bump next version to 2.5.0-SNAPSHOT
add 426bdca5a chore(deps): bump golang.org/x/text from 0.16.0 to 0.17.0
add 20925d39a chore(deps): bump golang.org/x/term from 0.22.0 to 0.23.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 (5d2c6d539)
\
N -- N -- N
refs/heads/dependabot/go_modules/golang.org/x/term-0.23.0 (20925d39a)
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.4.0.tgz | Bin 0 -> 289745 bytes
docs/charts/index.yaml | 29 ++++++++++++++++++++-
go.mod | 2 +-
go.sum | 4 +--
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 +--
13 files changed, 47 insertions(+), 20 deletions(-)
create mode 100644 docs/charts/camel-k-2.4.0.tgz
