This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to tag v2.12.0-nightly
in repository https://gitbox.apache.org/repos/asf/camel-k.git
*** WARNING: tag v2.12.0-nightly was modified! ***
from f6503ed96 (commit)
to eed159609 (commit)
discard f6503ed96 chore(ci): v2.12.0-nightly release updates
add 12d051e2d chore(deps): bump github.com/prometheus/client_golang
add 37a687914 chore(deps): bump sigs.k8s.io/gateway-api from 1.6.2 to 1.6.3
add 3942816b1 chore(trait): fail fast if registry is missing
add 4d0f02a65 chore(deps): bump golang.org/x/sync from 0.23.0 to 0.24.0
new eed159609 chore(ci): v2.12.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 (f6503ed96)
\
N -- N -- N refs/tags/v2.12.0-nightly (eed159609)
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.12.0-nightly.tgz | Bin 288520 -> 288519 bytes
docs/charts/index.yaml | 6 ++--
go.mod | 8 ++---
go.sum | 20 +++++------
pkg/controller/integration/build_test.go | 39 ++++++++-------------
.../bases/camel-k.clusterserviceversion.yaml | 2 +-
pkg/trait/builder.go | 17 ++++++---
pkg/trait/builder_test.go | 31 ++++++++++++++++
8 files changed, 77 insertions(+), 46 deletions(-)
