chore: release main

[release-please]

🤖 I have created a release beep boop

google-cloud-automl-v1beta1: 0.20.0

0.20.0 (2026-09-22)

⚠ BREAKING CHANGES

• Replace google-cloud-automl-v1beta1 with a tombstone (#36594)

Features

• Replace google-cloud-automl-v1beta1 with a tombstone (#36594)

google-cloud-backupdr-v1beta: 0.1.0

0.1.0 (2026-09-22)

Features

• onboard google/cloud/backupdr/v1beta API (#36598)

google-cloud-compute-v1: 3.12.0

3.12.0 (2026-09-22)

Features

• update API sources and regenerate (#36568)

---

This PR was generated with Release Please. See documentation.

[suztomo]

Why librarian.yaml does not have google-cloud-automl-v1beta1 change?

Because PR #36594 (feat!: Replace google-cloud-automl-v1beta1 with a tombstone, commit 8594399330) deleted the google-cloud-automl-v1beta1 entry from librarian.yaml:

--- a/librarian.yaml
+++ b/librarian.yaml
@@ -463,17 +463,6 @@ libraries:
     version: 1.2.0
     apis:
       - path: google/cloud/auditmanager/v1
-  - name: google-cloud-automl-v1beta1
-    version: 0.19.1
-    apis:
-      - path: google/cloud/automl/v1beta1
-        ruby:
-          ruby_cloud_opts:
-            ruby-cloud-env-prefix: AUTOML
-            ruby-cloud-namespace-override: AutoMl=AutoML;Automl=AutoML
-            ruby-cloud-path-override: auto_ml=automl
-    keep:
-      - lib/google/cloud/automl/v1beta1/_helpers.rb

Since google-cloud-automl-v1beta1 was replaced with a static tombstone gem, it was removed from librarian.yaml so Librarian will no longer regenerate it, while keeping it in release-please-config.json and .release-please-manifest.json so Release Please can publish the final 0.20.0 tombstone gem to RubyGems (updating version.rb, CHANGELOG.md, and .release-please-manifest.json).

[quartzmo]

LGTM

[release-please]

🤖 Created releases:

• google-cloud-automl-v1beta1/v0.20.0
• google-cloud-backupdr-v1beta/v0.1.0
• google-cloud-compute-v1/v3.12.0

🌻