This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/go_modules/go.uber.org/multierr-1.8.0
in repository https://gitbox.apache.org/repos/asf/camel-k.git.
discard 4d8f58e chore(deps): bump go.uber.org/multierr from 1.6.0 to 1.8.0
add 923f1ed fix: Propagate readiness condition message in KameletBinding
if present
add 1a9bf14 chore(deps): bump github.com/magiconair/properties from 1.8.5
to 1.8.6
add 1519583 chore(deps): bump go.uber.org/zap from 1.19.1 to 1.21.0
add ecd847f fix(ci): attempt for a single nightly release
add d3c7a77 chore(deps): bump github.com/gertd/go-pluralize from 0.1.1 to
0.2.0
add 94e5814 chore(deps): bump go.uber.org/multierr from 1.6.0 to 1.8.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 (4d8f58e)
\
N -- N -- N
refs/heads/dependabot/go_modules/go.uber.org/multierr-1.8.0 (94e5814)
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:
.github/workflows/nightly-tag.yaml | 39 --------------------------------
.github/workflows/release.yml | 18 +++++++--------
e2e/knative/kamelet_test.go | 16 ++++++++-----
go.mod | 2 +-
go.sum | 4 ++--
pkg/controller/kameletbinding/monitor.go | 6 ++++-
6 files changed, 27 insertions(+), 58 deletions(-)
delete mode 100644 .github/workflows/nightly-tag.yaml
