This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch update/sbt-assembly-2.2.0
in repository
https://gitbox.apache.org/repos/asf/pekko-persistence-cassandra.git
discard f005e3d Update sbt-assembly to 2.2.0
add 90171e7 Update scalafmt-core to 3.8.1 (#180)
add 0330464 remove duplicate dependencies (#181)
add 7dffb32 add lost dependency(scala-java8-compat) for doc (#182)
add 4a1bea6 Update sbt-java-formatter to 0.8.0 (#149)
add 61eb8c5 Pin Scala 3.3 LTS in scala steward
add cc853e0 Add repo condition to scala-steward.yml
add a50ac8e Update sbt-assembly to 2.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 (f005e3d)
\
N -- N -- N refs/heads/update/sbt-assembly-2.2.0 (a50ac8e)
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/scala-steward.yml | 3 ++-
.scala-steward.conf | 2 ++
.scalafmt.conf | 2 +-
build.sbt | 1 +
docs/src/test/java/jdoc/cleanup/CleanupDocExample.java | 5 ++---
project/Dependencies.scala | 4 +++-
project/plugins.sbt | 2 +-
7 files changed, 12 insertions(+), 7 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
