[pull] master from GoogleCloudPlatform:master - #1

* preparing release 25.2.0-bom

* 25.2.1-SNAPSHOT

* preparing release 25.3.0-bom

* 25.3.1-SNAPSHOT

* Xmx12g for Windows build

* gcp-lts-bom layer 1

* Google HTTP Client and API Client update

* Layer 2 libraries

* Exclude provided dependencies from the check

* trying google-cloud-pubsub 1.117.0

* added Beam 2.40.0

* increase xmx

* adding comments for supporting artifacts

* deps: Apache BCEL 6.6.1

* Removing MaximumLinkageErrorsTest for the libraries-bom

The Libraries BOM has moved to java-cloud-bom repository.

)

* preparing release 1.5.13-dependencies

* 1.5.14-SNAPSHOT

This will fix the problem of timeout:

```
Wrote dashboard for com.google.cloud:gcp-lts-bom:3.0.0-SNAPSHOT to target/com.google.cloud/gcp-lts-bom/snapshot

ERROR: Aborting VM command due to timeout of 14400 seconds
```

* Adjusting Allstar binary file alerts

* Not to add Maven wrapper JAR file

* install Java 11 in Kokoro MacOS

* follow error message

* test temurin

* skip javadoc job

…#2327)

* Remove BOM_SKIP_ARTIFACT_IDS

* fixing assertions

* Using jdk1.8.0_211 in kokoro-windows

* do not care new line characters

* chore: add temurin-install-testing

* chore: add ./test-all.sh for easier full suite execution

* chore: add snippet region tags and test-all.sh file

* chore: improve readme

* chore: LTS 5 layer 1 versions

* chore: update with most layer 2 versions

* chore: disable hbase connector dep (temporary)

* chore: update to latest appengine, gcs-connector, and android publisher

* chore: downgrade gcs-connector to 2.2.15

* chore: update to gRPC 1.55.3

* chore: guava 32.1.1, protobuf 3.23.4, auth 1.17.1

* chore: auth 1.19.0

* ci: add verbose mvn flag to failing Kokoro script

* chore: logging 3.15.6, spanner 6.43.2

* chore: pubsub 1.123.18

* chore: api-common 2.14.0

* chore: proto-google-common-protos 2.22.0

* chore: google-cloud-core 2.21.0

* chore: gax 2.31.0

* chore: beam 2.49.0, bigtable-hbase-beam 2.9.1

* chore: remove bigtable-hbase-beam (not yet available)

* chore: add bigtable-hbase-beam

* chore: java-bigtable 2.25.0

* chore: java-monitoring 3.22.0

* chore: java-datastore 2.15.1

* chore: guava 32.1.2-jre

* chore: 5.0.0-SNAPSHOT

* chore: fake update

* chore: @ignore LinkageCheckerMainIntegrationTest.testBom_java11

* chore: change expected linkage errors in grpc-netty-shaded from 4 to 5

* chore: change expected Linkage Checker rule errors in bom-project-using-spring-repository from 107 to 108

* chore: relocate linkage error assertion to JDK-version specific test

* chore: update LinkageCheckerMainIntegrationTest expected error count

* chore: remove unused import

* chore: remove outdated comments

* deps: Update library versions

* chore: Organize the dependencies

* deps: Update library versions

* deps: Use bigtable v2.30.0

* deps: Use Beam v2.52.0

* chore: Use Guava 32.1.3-jre

* chore: Update Beam to v2.53.0

* chore: Update bigtable-hbase-beam version to v2.12.0

* chore: Update to storage v2.30.2

b/323263307

Fix test failure by ignoring module-info in unique class check.

* deps: update layer 1 versions.

* update layer 1&2 versions.

* update beam version

* fix typo.

* test androidpublisher version.

* downgrade androidpublisher version for test.

* test androidpublisher version v3-rev20240328-2.0.0.

* chore: update androidpublisher to v3-rev20240418-2.0.0.

* update protobuf to 3.25.4

* chore: update Bigtable HBase Beam to 2.14.3

Fixes #2390

…t of artifacts (#2393)

* feat: Allow LinkageChecker to be called via exec:java goal

* feat: Add an Source filter to check if errors come from subset of files

* chore: Source Filter takes a list of artifacts

* chore: Update source filter to take in multiple args

* chore: Fix broken tests

* chore: Add comments and update artifacts equals method

* chore: Fix broken tests

* chore: Fix broken tests

* chore: Fix issues

* chore: Fix issues

* Revert "chore: Fix issues"

This reverts commit 3701953.

* chore: Fix issues

* chore: update comments to explain why not use problemFilter

* chore: Add test for source-filter

* chore: Add comments about including areArtifactsEquals helper method

)

* feat: LTS8

* fix version translate and vision

* update guava version

* temp update bigtable until we have new version

* update bigtable with correct version

* update protobuf to be version 3.25 + use exclusions

* update protobuf to be version 3.25.6

* exclude json pulled in by protobuf 3.25

* update beam to 2.64

* temporarily ignore downgrades

* fix versions of bigtable and storage

* update hbase version

* add hbase dependency

* revert typo

* Updated protobuf to 3.25.7

b/416442478

)

* feat: LTS 9

* fix: gcs-connector versions do not have prefixes from 3.0.0

* chore: update versions based on libraries-bom 26.62.0

* feat: update beam to 2.67.0

* feat: update bigtable-hbase-beam to v2.15.3

* Release Please file for gcp-lts-bom

The bootstrap-sha points to
8eb8233.
This is the parent commit of "Release 1.5.15-dependencies: Bumping to next version post release (#2408)".

LTS BOM 9.0.1 release happened after that.

New tag format is "<component>-v<version>". For example "gcp-lts-bom-v9.0.1" and "dependencies-v1.5.15".

* Maven profiles for release script

Becasue there was an independent step to sign artifaccts in the previous releases using Rapid, the pom.xml files didn't need to have GPG signing configurations. With new release setup, there's no independent step to sign artifacts. We need to use maven-gpg-plugin to sign artifacts.

* ci: 6.0.x-lts branch as test in the branches

7.0.x-lts and 6.0.x-lts are added.

* ci: Bootstrap sha that includes LTS 7 and 6

7.0.x-lts branch is still live. The 6.0.x-lts branch is for testing of
the new release script.

* ci: use java-backport in Release Please branches

java-lts release type was outdated (go/backport-releases#2-run-the-release-brancher-cli-tool).
It created a strange pull request with "-sp.1" suffix version.

* ci: release-type should be read by release-please-config

The Libraries BOM has moved to the java-cloud-bom repository.
We have cloud-lts-bom still in this repository but it's not released
as part of the root project. Removing it from the root pom.xml.

The dashboard from the dashboard module is no longer used. Let's stop
the periodic build job.

The linkage-monitor directory is not released as part of the root
module.

This change also fixes the CI of the Gradle plugin.
The Gradle plugin is published to Gradle plugin portal, not Maven
Central. https://plugins.gradle.org/plugin/com.google.cloud.tools.linkagechecker

* chore: add release-please config for protobuf-4.x

* feat: configure rc releases to be on prerelease mode

* fix: next release candidate

* chore: cleanup release-please config

- Remove redundant options already declared at the top level.\n- Remove bumpMinorPreMajor for repositories after the first major release.

* refactor: move common release-please options to top level

* revert: revert changes to release-please-config.json

* chore: update cloud-lts-bom versions

* Update pom.xml

* chore: align versions to resolve downgrades and enable no-downgrade check

* chore: revert google-http-client to 2.1.0 to avoid downgrades

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>