This is an automated email from the ASF dual-hosted git repository.
fanningpj pushed a change to branch update/scalafmt-core-3.7.17
in repository https://gitbox.apache.org/repos/asf/pekko-projection.git
omit ec0c8dd Update scalafmt-core to 3.7.17
add 28ef55d Update hibernate-core to 5.6.15.Final
add ee803e2 Update mysql-connector-java to 8.3.0
add deb3e6f Update scalafmt-native github action (#143)
new 6c6bbab Update scalafmt-core to 3.7.17
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 (ec0c8dd)
\
N -- N -- N refs/heads/update/scalafmt-core-3.7.17 (6c6bbab)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.github/workflows/format.yml | 3 +--
project/Dependencies.scala | 4 ++--
2 files changed, 3 insertions(+), 4 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
