chore(deps): bump google-cloud-error-reporting from 1.4.0 to 1.16.0 - #6122
chore(deps): bump google-cloud-error-reporting from 1.4.0 to 1.16.0#6122dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [google-cloud-error-reporting](https://github.com/googleapis/google-cloud-python) from 1.4.0 to 1.16.0. - [Release notes](https://github.com/googleapis/google-cloud-python/releases) - [Changelog](https://github.com/googleapis/google-cloud-python/blob/main/packages/gcp-sphinx-docfx-yaml/CHANGELOG.md) - [Commits](googleapis/google-cloud-python@storage-1.4.0...google-cloud-error-reporting-v1.16.0) --- updated-dependencies: - dependency-name: google-cloud-error-reporting dependency-version: 1.16.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
🟡 Waiting for changesLast updated: 2026-09-01 00:54 UTC |
rtibblesbot
left a comment
rtibblesbot
left a comment
There was a problem hiding this comment.
PR #6122 — google-cloud-error-reporting 1.4.0 → 1.16.0 (production, requirements.in:17, uv-compiled requirements.txt). Minor bump direct; drags transitive google-cloud-logging 2.7.1 → 3.16.0 across a major boundary and adds opentelemetry-api==1.44.0. CI passing.
- Breaking changes: none to the handwritten
Client. Range is GAPIC regeneration, protobuf 5/6/7 allowances, mTLS, Python 3.12–3.14 support, floor raises (google-api-core>=2.17.1, Python >=3.10 — CI and both Dockerfiles are 3.10). - Deprecations:
credentials_fileargument (1.13.0), unused here. - Security fixes: none in range.
- Compatibility:
contentcuration/contentcuration/middleware/error_reporting.py:8-15is the only consumer. At 1.16.0Client.__init__still takes_use_grpc=Nonewith the same_USE_GRPCfallback,report_exception(http_context=None, user=None)is unchanged,from_service_account_jsonstill comes fromgoogle-cloud-core(2.6.0, untouched). No code changes required. - The changelog dependabot pasted into the PR body is
gcp-sphinx-docfx-yaml's, not this package's — monorepo mis-resolution.
See the inline note on the transitive google-cloud-logging major.
@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly
How was this generated?
Ran a dependency-update review pipeline over the version bump:
- Classified the bump by semver (patch / minor / major) and dependency type (production vs. development)
- Extracted the changelog and release notes across the version range
- Assessed compatibility with this project's usage and whether any code changes are required
- Treated CI as the primary safety net
- Scaled the review depth to the update's risk
- Chose the verdict from semver risk, changelog findings, and CI status
| google-cloud-kms==2.24.2 | ||
| # via -r requirements.in | ||
| google-cloud-logging==2.7.1 | ||
| google-cloud-logging==3.16.0 |
There was a problem hiding this comment.
suggestion: Major bump sitting on the live error path, untested by CI. Because the middleware passes _use_grpc=False, reports go through _ErrorReportingLoggingAPI, which builds a google.cloud.logging.Client(...) and calls logger("errors").log_struct(...).
Mitigating: nothing in contentcuration/ imports google.cloud.logging directly; error-reporting 1.16.0 declares google-cloud-logging>=3.9.0, so upstream tests the pairing; 3.0.0's breaking changes are in the handler classes (AppEngineHandler/ContainerEngineHandler, setup_logging) and json-payload/resource-inference behavior — not the Client(...) + log_struct surface used here.
One behavior change to know about: 3.0.0 infers a default monitored resource per logger instead of defaulting to global, so the resource label on Error Reporting entries changes in production.
CI covers none of this — the middleware is only installed when GCLOUD_ERROR_REPORTING is set (contentcuration/settings.py:156) and no test imports it. Worth one manual report_exception() against a staging project before this reaches production.
| exceptiongroup==1.3.1 | ||
| # via celery | ||
| google-api-core[grpc]==2.30.0 | ||
| google-api-core==2.30.0 |
There was a problem hiding this comment.
nitpick: Annotation-only — the [grpc] extras markers dropped here and on googleapis-common-protos don't change the install set. grpcio==1.78.0 and grpcio-status==1.62.3 remain their own pinned lines, so uv pip sync installs the same packages. Noting it so it isn't read as grpc support being dropped.
1 participant
Bumps google-cloud-error-reporting from 1.4.0 to 1.16.0.
Changelog
Sourced from google-cloud-error-reporting's changelog.
... (truncated)
Commits
a5ad18cchore: release main (#17482)f6937b3chore(main): release google-cloud-bigtable 2.39.0 (#17497)172302bci(bigquery-storage): fixcore_deps_from_sourceandprerelease_depsby in...e726878fix(bigframes): world-readable temp zip in create_cloud_function (#17522)2f893b1fix: bump@angular/common,@angular/forms,@angular/platform-browserand@ang...f23063ffix: bump langsmith from 0.8.0 to 0.8.18 in /packages/bigframes (#17518)6fc45e3fix: bump undici and@angular/buildin /packages/bigframes/bigframes/display/...36b5b7efix: bump msgpack from 1.1.1 to 1.2.1 in /packages/bigframes (#17520)11de939tests: add Python 3.15 pre-release testing (#17517)0258405fix(bigquery): close GAPIC storage transport and auth sessions to prevent soc...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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)