This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch update/sbt-license-report-1.7.0
in repository https://gitbox.apache.org/repos/asf/pekko-connectors.git


 discard 50a6aed62 Update sbt-license-report to 1.7.0
     add 7fede7d7b Update amazon-kinesis-client to 3.0.0 (#898)
     add 8db5e83c8 Update auth, dynamodb, eventbridge, firehose, ... to 2.29.9 
(#897)
     add 54dace838 Update sbt, scripted-plugin to 1.10.5 (#896)
     add 825625bdd Update mongo-scala-driver to 5.2.1 (#895)
     add 91e5b1cfe Update kudu-client to 1.17.1 (#894)
     add bf5545d9b don't link validate license report (#899)
     add 4a175fef7 remove TODO in workflow (#900)
     add 0ffb54515 pekko-grpc 1.1.1 (#892)
     add 39b8bcb01 Update sbt-license-report to 1.7.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   (50a6aed62)
            \
             N -- N -- N   refs/heads/update/sbt-license-report-1.7.0 
(39b8bcb01)

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/check-build-test.yml |  4 ---
 .github/workflows/link-validator.yml   |  2 +-
 project/Dependencies.scala             |  8 +++---
 project/build.properties               |  2 +-
 project/plugins.sbt                    |  2 +-
 scripts/link-validator.conf            | 48 ++++------------------------------
 6 files changed, 12 insertions(+), 54 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to