This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch update/pekko-actor-1.2.1
in repository https://gitbox.apache.org/repos/asf/pekko-management.git
omit 62c965bc Update pekko-actor, pekko-cluster, ... to 1.2.1
add b78e2785 Update ecs to 2.34.9 (#519)
add e6d501c3 Update sbt-native-packager to 1.11.4 (#518)
add 135096a8 Update aws-java-sdk-ec2, aws-java-sdk-ecs to 1.12.792 (#517)
add ed2a0385 Update logback-classic to 1.5.19 (#516)
add 3ba77e5f Update pekko-actor, pekko-cluster, ... to 1.2.1
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 (62c965bc)
\
N -- N -- N refs/heads/update/pekko-actor-1.2.1 (3ba77e5f)
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 +-
project/Dependencies.scala | 6 +++---
project/plugins.sbt | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
