This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch update/mssql-jdbc-12.6.1.jre11
in repository https://gitbox.apache.org/repos/asf/pekko-projection.git
discard 007a8ed Update mssql-jdbc to 12.6.1.jre11
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)
add a4bac54 Update mssql-jdbc to 12.6.1.jre11
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 (007a8ed)
\
N -- N -- N refs/heads/update/mssql-jdbc-12.6.1.jre11 (a4bac54)
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/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]
