This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/go_modules/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring-0.55.0
in repository https://gitbox.apache.org/repos/asf/camel-k.git.
discard 4384237 chore(deps): bump
github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring
add a3c7d5f chore(deps): bump github.com/rs/xid from 1.2.1 to 1.3.0
add 4b883ba chore(deps): bump github.com/prometheus/client_golang
add f5f81b7 chore(deps): bump
github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring
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 (4384237)
\
N -- N -- N
refs/heads/dependabot/go_modules/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring-0.55.0
(f5f81b7)
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:
go.mod | 4 ++--
go.sum | 10 ++++++----
2 files changed, 8 insertions(+), 6 deletions(-)
