This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch update/java-client-3.5.2
in repository https://gitbox.apache.org/repos/asf/incubator-pekko-connectors.git
omit d450334d6 Update java-client to 3.5.2
add 265868166 Update sbt-pekko-build to 0.3.3 (#429)
add e26740207 use hadoop 3.3.6 (hdfs connector) (#435)
add f49022898 update coursier action (#436)
add 4223ac20b Use scope config for compute-engine auth
add f2e2159b3 Update java-client to 3.5.2
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 (d450334d6)
\
N -- N -- N refs/heads/update/java-client-3.5.2 (f2e2159b3)
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 | 6 +++---
.github/workflows/headers.yml | 2 +-
.github/workflows/link-validator.yml | 2 +-
.github/workflows/nightly-builds.yaml | 2 +-
.github/workflows/nightly-pekko-1.1-builds.yaml | 2 +-
.scala-steward.conf | 2 ++
.../google/auth/ComputeEngineCredentials.scala | 9 +++++----
.../stream/connectors/google/auth/Credentials.scala | 6 ++++--
.../connectors/google/auth/GoogleComputeMetadata.scala | 17 +++++++++++++----
project/Dependencies.scala | 2 +-
project/plugins.sbt | 2 +-
11 files changed, 33 insertions(+), 19 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
