This is an automated email from the ASF dual-hosted git repository.
fanningpj pushed a change to branch update/scalatest-3.2.18
in repository https://gitbox.apache.org/repos/asf/pekko-persistence-r2dbc.git
discard 9ee8d34 Merge branch 'main' into update/scalatest-3.2.18
discard fd02e0b Update scalatest to 3.2.18
add aa46c4f Update sbt-site-paradox to 1.7.0 (#110)
add 3994043 Update scalatest to 3.2.18
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 (9ee8d34)
\
N -- N -- N refs/heads/update/scalatest-3.2.18 (3994043)
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:
project/Dependencies.scala | 2 --
project/plugins.sbt | 2 +-
2 files changed, 1 insertion(+), 3 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
