chore(deps): bump protobuf from 4.21.12 to 4.25.8

[dependabot]

Bumps protobuf from 4.21.12 to 4.25.8.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.

[curtismorales]

@dependabot recreate

[dataops-ci-bot]

Integration report for "chore(deps): bump protobuf from 4.21.12 to 4.25.8"

sql.diff

Click to expand!

Only in /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod: firefox_desktop_stable
Only in /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod: org_mozilla_firefox_stable
Only in /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod: org_mozilla_ios_firefox_stable
Only in /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod: telemetry_stable
diff -bur --no-dereference --new-file /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod/firefox_desktop_stable/baseline_v1/bigconfig.yml /tmp/workspace/generated-sql/sql/moz-fx-data-shared-prod/firefox_desktop_stable/baseline_v1/bigconfig.yml
--- /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod/firefox_desktop_stable/baseline_v1/bigconfig.yml	2025-12-08 07:18:07.000000000 +0000
+++ /tmp/workspace/generated-sql/sql/moz-fx-data-shared-prod/firefox_desktop_stable/baseline_v1/bigconfig.yml	1970-01-01 00:00:00.000000000 +0000
@@ -1,12 +0,0 @@
-type: BIGCONFIG_FILE
-tag_deployments:
-- collection:
-    name: Operational Checks
-    notification_channels:
-    - slack: '#de-bigeye-triage'
-  deployments:
-  - column_selectors:
-    - name: moz-fx-data-shared-prod.moz-fx-data-shared-prod.firefox_desktop_stable.baseline_v1.*
-    metrics:
-    - saved_metric_id: volume
-    - saved_metric_id: freshness
diff -bur --no-dereference --new-file /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod/firefox_desktop_stable/baseline_v1/metadata.yaml /tmp/workspace/generated-sql/sql/moz-fx-data-shared-prod/firefox_desktop_stable/baseline_v1/metadata.yaml
--- /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod/firefox_desktop_stable/baseline_v1/metadata.yaml	2025-12-08 07:18:07.000000000 +0000
+++ /tmp/workspace/generated-sql/sql/moz-fx-data-shared-prod/firefox_desktop_stable/baseline_v1/metadata.yaml	1970-01-01 00:00:00.000000000 +0000
@@ -1,12 +0,0 @@
-friendly_name: Baseline
-description: |-
-  There are two main namespaces in BigQuery for used during telemetry ingestion process.
-  Those namespaces end with _live and _stable . _live is the initial landing zone in BigQuery for our ping data
-  coming from our ingestion-sink which uses a smaller time window to batch telemetry data together.
-  However, there is a potential for duplicate entries in this dataset which is why once a day copy_deduplicate DAG performs de-duplication of this data
-  and saves the result in the corresponding _stable namespace (which also acts as long term storage of this raw data).
-  These BigEye checks add freshness and volume checks to these stable tables.
-
-monitoring:
-  enabled: True
-  collection: Operational Checks
\ No newline at end of file
diff -bur --no-dereference --new-file /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod/org_mozilla_firefox_stable/baseline_v1/bigconfig.yml /tmp/workspace/generated-sql/sql/moz-fx-data-shared-prod/org_mozilla_firefox_stable/baseline_v1/bigconfig.yml
--- /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod/org_mozilla_firefox_stable/baseline_v1/bigconfig.yml	2025-12-08 07:18:07.000000000 +0000
+++ /tmp/workspace/generated-sql/sql/moz-fx-data-shared-prod/org_mozilla_firefox_stable/baseline_v1/bigconfig.yml	1970-01-01 00:00:00.000000000 +0000
@@ -1,12 +0,0 @@
-type: BIGCONFIG_FILE
-tag_deployments:
-- collection:
-    name: Operational Checks
-    notification_channels:
-    - slack: '#de-bigeye-triage'
-  deployments:
-  - column_selectors:
-    - name: moz-fx-data-shared-prod.moz-fx-data-shared-prod.org_mozilla_firefox_stable.baseline_v1.*
-    metrics:
-    - saved_metric_id: volume
-    - saved_metric_id: freshness
diff -bur --no-dereference --new-file /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod/org_mozilla_firefox_stable/baseline_v1/metadata.yaml /tmp/workspace/generated-sql/sql/moz-fx-data-shared-prod/org_mozilla_firefox_stable/baseline_v1/metadata.yaml
--- /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod/org_mozilla_firefox_stable/baseline_v1/metadata.yaml	2025-12-08 07:18:07.000000000 +0000
+++ /tmp/workspace/generated-sql/sql/moz-fx-data-shared-prod/org_mozilla_firefox_stable/baseline_v1/metadata.yaml	1970-01-01 00:00:00.000000000 +0000
@@ -1,12 +0,0 @@
-friendly_name: Baseline
-description: |-
-  There are two main namespaces in BigQuery for used during telemetry ingestion process.
-  Those namespaces end with _live and _stable . _live is the initial landing zone in BigQuery for our ping data
-  coming from our ingestion-sink which uses a smaller time window to batch telemetry data together.
-  However, there is a potential for duplicate entries in this dataset which is why once a day copy_deduplicate DAG performs de-duplication of this data
-  and saves the result in the corresponding _stable namespace (which also acts as long term storage of this raw data).
-  These BigEye checks add freshness and volume checks to these stable tables.
-
-monitoring:
-  enabled: True
-  collection: Operational Checks
\ No newline at end of file
diff -bur --no-dereference --new-file /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod/org_mozilla_ios_firefox_stable/baseline_v1/bigconfig.yml /tmp/workspace/generated-sql/sql/moz-fx-data-shared-prod/org_mozilla_ios_firefox_stable/baseline_v1/bigconfig.yml
--- /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod/org_mozilla_ios_firefox_stable/baseline_v1/bigconfig.yml	2025-12-08 07:18:07.000000000 +0000
+++ /tmp/workspace/generated-sql/sql/moz-fx-data-shared-prod/org_mozilla_ios_firefox_stable/baseline_v1/bigconfig.yml	1970-01-01 00:00:00.000000000 +0000
@@ -1,12 +0,0 @@
-type: BIGCONFIG_FILE
-tag_deployments:
-- collection:
-    name: Operational Checks
-    notification_channels:
-    - slack: '#de-bigeye-triage'
-  deployments:
-  - column_selectors:
-    - name: moz-fx-data-shared-prod.moz-fx-data-shared-prod.org_mozilla_ios_firefox_stable.baseline_v1.*
-    metrics:
-    - saved_metric_id: volume
-    - saved_metric_id: freshness
diff -bur --no-dereference --new-file /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod/org_mozilla_ios_firefox_stable/baseline_v1/metadata.yaml /tmp/workspace/generated-sql/sql/moz-fx-data-shared-prod/org_mozilla_ios_firefox_stable/baseline_v1/metadata.yaml
--- /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod/org_mozilla_ios_firefox_stable/baseline_v1/metadata.yaml	2025-12-08 07:18:07.000000000 +0000
+++ /tmp/workspace/generated-sql/sql/moz-fx-data-shared-prod/org_mozilla_ios_firefox_stable/baseline_v1/metadata.yaml	1970-01-01 00:00:00.000000000 +0000
@@ -1,12 +0,0 @@
-friendly_name: Baseline
-description: |-
-  There are two main namespaces in BigQuery for used during telemetry ingestion process.
-  Those namespaces end with _live and _stable . _live is the initial landing zone in BigQuery for our ping data
-  coming from our ingestion-sink which uses a smaller time window to batch telemetry data together.
-  However, there is a potential for duplicate entries in this dataset which is why once a day copy_deduplicate DAG performs de-duplication of this data
-  and saves the result in the corresponding _stable namespace (which also acts as long term storage of this raw data).
-  These BigEye checks add freshness and volume checks to these stable tables.
-
-monitoring:
-  enabled: True
-  collection: Operational Checks
\ No newline at end of file
diff -bur --no-dereference --new-file /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod/telemetry_stable/main_v4/bigconfig.yml /tmp/workspace/generated-sql/sql/moz-fx-data-shared-prod/telemetry_stable/main_v4/bigconfig.yml
--- /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod/telemetry_stable/main_v4/bigconfig.yml	2025-12-08 07:18:07.000000000 +0000
+++ /tmp/workspace/generated-sql/sql/moz-fx-data-shared-prod/telemetry_stable/main_v4/bigconfig.yml	1970-01-01 00:00:00.000000000 +0000
@@ -1,12 +0,0 @@
-type: BIGCONFIG_FILE
-tag_deployments:
-- collection:
-    name: Operational Checks
-    notification_channels:
-    - slack: '#de-bigeye-triage'
-  deployments:
-  - column_selectors:
-    - name: moz-fx-data-shared-prod.moz-fx-data-shared-prod.telemetry_stable.main_v4.*
-    metrics:
-    - saved_metric_id: volume
-    - saved_metric_id: freshness
diff -bur --no-dereference --new-file /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod/telemetry_stable/main_v4/metadata.yaml /tmp/workspace/generated-sql/sql/moz-fx-data-shared-prod/telemetry_stable/main_v4/metadata.yaml
--- /tmp/workspace/main-generated-sql/sql/moz-fx-data-shared-prod/telemetry_stable/main_v4/metadata.yaml	2025-12-08 07:18:07.000000000 +0000
+++ /tmp/workspace/generated-sql/sql/moz-fx-data-shared-prod/telemetry_stable/main_v4/metadata.yaml	1970-01-01 00:00:00.000000000 +0000
@@ -1,12 +0,0 @@
-friendly_name: Main
-description: |-
-  There are two main namespaces in BigQuery for used during telemetry ingestion process.
-  Those namespaces end with _live and _stable . _live is the initial landing zone in BigQuery for our ping data
-  coming from our ingestion-sink which uses a smaller time window to batch telemetry data together.
-  However, there is a potential for duplicate entries in this dataset which is why once a day copy_deduplicate DAG performs de-duplication of this data
-  and saves the result in the corresponding _stable namespace (which also acts as long term storage of this raw data).
-  These BigEye checks add freshness and volume checks to these stable tables.
-
-monitoring:
-  enabled: True
-  collection: Operational Checks
\ No newline at end of file

Link to full diff