This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/go_modules/github.com/container-tools/spectrum-0.6.10
in repository https://gitbox.apache.org/repos/asf/camel-k.git
omit 8c53014cc chore(deps): bump github.com/container-tools/spectrum
add 32527c10f fix: align process to latest ck runtime changes
add dde540416 chore: minor descriptions
add cbda43804 fix(operator): do not panic if cannot set GOMAXPROCS
add 3717043a3 fix(ci): fill kamelets catalog
add 7eb0d25d0 fix(ci): make update-docs
add 94d9cd3a2 chore(deps): bump github.com/container-tools/spectrum
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 (8c53014cc)
\
N -- N -- N
refs/heads/dependabot/go_modules/github.com/container-tools/spectrum-0.6.10
(94d9cd3a2)
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-automatic-updates.yml | 6 +++---
docs/antora.yml | 2 +-
pkg/cmd/operator/operator.go | 4 +++-
...og-3.20.1-SNAPSHOT.yaml => camel-catalog-2.16.0-SNAPSHOT.yaml} | 6 +++---
script/Makefile | 2 +-
script/update_default_camel.sh | 8 +++++---
6 files changed, 16 insertions(+), 12 deletions(-)
rename resources/{camel-catalog-3.20.1-SNAPSHOT.yaml =>
camel-catalog-2.16.0-SNAPSHOT.yaml} (99%)
