This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch update/pekko-actor-1.2.0
in repository https://gitbox.apache.org/repos/asf/pekko-management.git
discard d63864f9 Update pekko-actor, pekko-cluster, ... to 1.2.0
add db7826d7 Update ecs to 2.33.7 (#503)
add 10cd67fe Update mockito-core to 5.19.0 (#502)
add fe2cc805 Update jackson-core, jackson-databind to 2.20.0 (#497)
add bd484f27 Update sbt-license-report to 1.8.0 (#498)
add e37de22e upgrade wiremock (#504)
add abe3a02c Update logback-classic to 1.5.18 (#495)
add c60410b1 Update pekko-actor, pekko-cluster, ... to 1.2.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 (d63864f9)
\
N -- N -- N refs/heads/update/pekko-actor-1.2.0 (c60410b1)
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:
integration-test/kubernetes-api-java/pom.xml | 2 +-
.../loglevels/logback/LogLevelRoutes.scala | 3 +++
project/Dependencies.scala | 30 ++++------------------
project/plugins.sbt | 2 +-
4 files changed, 10 insertions(+), 27 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
