chore(deps): update module github.com/grpc-ecosystem/grpc-gateway/v2 to v2.30.0 (main)

[renovate-sh-app]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/grpc-ecosystem/grpc-gateway/v2	v2.29.0 → v2.30.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

grpc-ecosystem/grpc-gateway (github.com/grpc-ecosystem/grpc-gateway/v2)

v2.30.0

Compare Source

New Features

• protoc-gen-openapiv3: Brand new minimal OpenAPI v3 generator (#​6623), plus follow-ups:
  • Visibility selectors (#​6673)
  • disable_default_errors option (#​6672)
  • Annotation support (#​6681)
  • Improved plugin error surfacing (#​6937)
  • field_behavior REQUIRED support for query parameters (#​7180) — @​maydietwice
• openapiv3-merge: New standalone tool for merging OpenAPI v3 documents (#​6771) — @​johanbrandhorst
• protoc-gen-openapiv2 moved to the protoc toolchain (#​6988) — @​EliSauder

Fixes

Change	PR	Contributor
OpenAPI v2: messages sorted before rendering definitions for determinism	#​6732	@​alliasgher
OpenAPI v2: enum comments now go to description instead of title	#​6785	@​superShen0916
OpenAPI v2: include field schema metadata on parameters	#​6894	@​puneetdixit200
OpenAPI v2: omit empty body objects for nested path parameters	#​7065	@​alliasgher
OpenAPI v3: omit empty body objects for nested path parameters	#​7068	@​alliasgher
OpenAPI v2: preserve x-nullable when use_allof_for_refs wraps a $ref	#​7026	@​pkhanaljc
OpenAPI v2: fix path joining for colon-prefixed segments	#​7191	@​Ritik100-AIT
Prioritize OpenAPI config options over proto options	#​6973	@​maskedmaxx
Support Service doc comments for OpenAPI/Swagger generation	#​6200	@​majiayu000
Fix nested body path initialization for oneof fields	#​6948	@​cyphercodes
Remove redundant enum assignment for nested proto3 fields	#​7059	@​abhishek-dalbanjan
Drain request only after ParseForm in generated code	#​7192	@​paskozdilar
Support field extensions with use_allof_for_refs	#​3100	@​same-id
Ignore M import-path mappings in openapiv3 plugin params	#​6936	@​johanbrandhorst

Documentation

• Clarify HttpBody download usage (#​6904) — @​ketpatil77
• Clarify Go tool dependency options (#​7042) — @​hawk-roy
• Add a runnable OpenTelemetry tracing example (#​7110) — @​hsdfat
• Fix SLSA link in README (#​7149) — @​ZayanKhan-12
• Explain Buf strategy for shared API config (#​7147) — @​dlanov

Tests / CI / Infra

• Add test coverage for slice converters in convert.go (#​7041) — @​viniciusmtsantos
• Remove Java swagger generator test dependency (#​6735) — @​johanbrandhorst
• CI improvements — go-version-file usage, release workflow tag input, checkout ref fixes, node_test timeouts, Node 22 LTS for browser tests (avoids a Node 24 zlib hang) (#​6627, #​6632, #​6633, #​6867, #​6868) — @​johanbrandhorst
• Better Bazel caching; auto-merge job for dependabot PRs (#​6667, #​6668) — @​johanbrandhorst
• Run gazelle on openapiv3 files; add missing Bazel files (#​6734, #​6738) — @​johanbrandhorst

New Contributors

@​alliasgher, @​superShen0916, @​puneetdixit200, @​ketpatil77, @​EliSauder, @​maskedmaxx, @​hawk-roy, @​viniciusmtsantos, @​cyphercodes, @​abhishek-dalbanjan, @​hsdfat, @​ZayanKhan-12, @​dlanov, @​maydietwice, @​pkhanaljc, @​Ritik100-AIT

---

Full Changelog: grpc-ecosystem/grpc-gateway@v2.29.0...v2.30.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

Need help?

You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.

[renovate-sh-app]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 17 additional dependencies were updated

Details:

Package	Change
go.opentelemetry.io/otel	v1.44.0 -> v1.45.0
go.opentelemetry.io/otel/metric	v1.44.0 -> v1.45.0
go.opentelemetry.io/otel/sdk	v1.44.0 -> v1.45.0
go.opentelemetry.io/otel/trace	v1.44.0 -> v1.45.0
google.golang.org/grpc	v1.82.1 -> v1.83.0
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc	v0.69.0 -> v0.70.0
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp	v0.69.0 -> v0.70.0
google.golang.org/genproto/googleapis/rpc	v0.0.0-20260630182238-925bb5da69e7 -> v0.0.0-20260803160001-6ac0973c030d
cel.dev/expr	v0.25.1 -> v0.25.2
github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp	v1.32.0 -> v1.33.0
github.com/go-logr/logr	v1.4.3 -> v1.4.4
github.com/go-openapi/validate	v0.26.0 -> v0.26.1
github.com/spiffe/go-spiffe/v2	v2.6.0 -> v2.7.0
go.opentelemetry.io/contrib/detectors/gcp	v1.43.0 -> v1.44.0
go.opentelemetry.io/otel/exporters/stdout/stdouttrace	v1.44.0 -> v1.45.0
go.opentelemetry.io/otel/sdk/metric	v1.44.0 -> v1.45.0
google.golang.org/genproto/googleapis/api	v0.0.0-20260630182238-925bb5da69e7 -> v0.0.0-20260803160001-6ac0973c030d

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: OTEL SDK 1.45.0 (pulled in transitively by grpc-gateway v2.30.0) uses semconv v1.43.0 in resource.Default(), which conflicts with dskit's tracing.NewResource still importing semconv/v1.41.0, so resource.Merge fails with a schema-URL mismatch in pkg/tracing tests. Next step: bump github.com/grafana/dskit to a revision whose tracing package uses semconv/v1.43.0 (latest dskit still uses 1.41.0) and re-tidy, or hold this Renovate PR until such a dskit release is available.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: grpc-gateway v2.30.0 transitively forces go.opentelemetry.io/otel/sdk to v1.45.0, whose resource.Default() now uses semconv/v1.43.0, conflicting with grafana/dskit/tracing (still on semconv/v1.41.0) when it calls resource.Merge — breaking pkg/tracing tests with ErrSchemaURLConflict. Fix requires an upstream dskit bump to semconv/v1.43.0 (latest dskit still uses v1.41.0), which is out of scope for this Renovate bump.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: The grpc-gateway v2.30.0 bump forces otel v1.44→v1.45; otel/sdk v1.45's resource.Default() uses semconv v1.43.0 while dskit's tracing.NewResource still merges in a resource built from semconv v1.41.0, so resource.Merge returns ErrSchemaURLConflict and every pkg/tracing test that calls InstallOTelOrJaegerFromEnv fails. Next step for a human: land a dskit change that bumps its tracing semconv to v1.43.0 (or otherwise avoids the merge conflict) and then rebase this PR onto that dskit version — a tempo-only fix isn't safe.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: pkg/tracing tests fail with conflicting Schema URL: .../1.43.0 and .../1.41.0 because OTel SDK v1.45.0 (pulled in transitively by grpc-gateway v2.30.0) moved resource.Default() to semconv v1.43.0, while dskit's tracing.NewResource still merges it with semconv/v1.41.0.SchemaURL. No released dskit version yet uses v1.43.0, so this needs an upstream dskit bump (or a temporary replace pinning OTel back to v1.44.0) before the PR can go green.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: grpc-gateway v2.30.0 transitively bumps OTel SDK to v1.45.0, whose resource.Default() now uses semconv/v1.43.0; grafana/dskit's tracing package still uses semconv/v1.41.0 in resource.Merge, so InstallOTelOrJaegerFromEnv fails with ErrSchemaURLConflict. Fix belongs upstream in grafana/dskit (bump its semconv to v1.43.0 or expose a schema-URL override); wait for that release before merging this Renovate PR.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: grpc-gateway v2.30.0 transitively bumps go.opentelemetry.io/otel to v1.45.0, whose resource.Default() uses semconv/v1.43.0, which conflicts with dskit's tracing.NewResource() that still uses semconv/v1.41.0 — causing tempo's own tracing setup to fail with 'conflicting Schema URL'. Fixing requires bumping grafana/dskit to a version using semconv/v1.43.0, but that cascades ~30 unrelated transitive upgrades and is out of scope; a human should raise a separate dskit bump PR first (or bump dskit alongside grpc-gateway here).

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: The grpc-gateway bump transitively pulled go.opentelemetry.io/otel* to v1.45.0, whose sdk/resource now uses semconv/v1.43.0.SchemaURL, conflicting with the vendored dskit tracing which still uses semconv/v1.41.0.SchemaURL — resource.Merge fails in pkg/tracing tests. Next step: bump github.com/grafana/dskit to a version that uses semconv/v1.43.0 (or pin otel back to v1.44.0 via replace) — beyond the scope of a Renovate-only fix. The unrelated TestCompactionProvider_EmptyStart failure looks flaky and was not investigated further.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: grpc-gateway v2.30.0 transitively requires go.opentelemetry.io/otel/sdk v1.45.0, whose resource.Default() moved to semconv v1.43.0, which conflicts with the schema URL used by the vendored grafana/dskit tracing helper (still on semconv v1.41.0) and breaks every pkg/tracing test. Fix requires bumping grafana/dskit to a version that uses semconv v1.43.0 (or later) before this Renovate update can land — pinning otel back to v1.44.0 is undone by go mod tidy because grpc-gateway v2.30.0 hard-requires v1.45.0.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: pkg/tracing tests fail with 'conflicting Schema URL: 1.43.0 and 1.41.0' because otel 1.45.0's resource.Default() now uses semconv 1.43.0 while the vendored dskit tracing.NewResource still uses semconv 1.41.0. Next step for a human: bump github.com/grafana/dskit to a revision that uses semconv v1.43.0 (e.g. v0.0.0-20260821075218-4fba1e581d65 or later) as a coordinated update, and reconcile the resulting otelzap bridge break (log.KeyValue/log.Value moved) — out of scope for a grpc-gateway auto-fix.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: The grpc-gateway/v2 bump transitively updated go.opentelemetry.io/otel/sdk from v1.44.0 to v1.45.0, whose resource.Default() now uses semconv/v1.43.0, while vendored github.com/grafana/dskit/tracing.NewResource still uses semconv/v1.41.0 and calls resource.Merge — producing ErrSchemaURLConflict that dskit propagates as "failed to initialise trace resource". The fix belongs upstream in dskit (bump its semconv to v1.43.0) or requires pinning otel/sdk back to v1.44.0 via replace directives, either of which is outside the scope of a Renovate auto-fix.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: grpc-gateway v2.30.0 pulls OTel SDK v1.45.0 whose resource.Default() uses semconv schema URL v1.43.0, but vendored dskit's tracing.NewResource still hard-codes semconv/v1.41.0, so resource.Merge fails with a schema URL conflict inside dskit — unreachable from tempo. A human needs to bump github.com/grafana/dskit to a version using semconv/v1.43.0 (e.g. v0.0.0-20260824024943-e68091815c4c) alongside this grpc-gateway update, or land the dskit bump first.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: The OTel SDK v1.44.0→v1.45.0 bump (transitive to grpc-gateway) moved resource.Default() to semconv v1.43.0, but vendored dskit tracing still imports semconv v1.41.0, so its NewResource errors on conflicting Schema URL and every tempo boot (unit tests in pkg/tracing + all e2e binaries) fails; fix belongs in dskit (bump semconv to v1.43.0) or as an OTel SDK rollback, out of scope for a Renovate-PR fix.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: The pkg/tracing failure is a real regression: grpc-gateway v2.30 transitively requires go.opentelemetry.io/otel/sdk v1.45.0, whose resource.Default() emits schema URL 1.43.0 and conflicts with vendored grafana/dskit/tracing (still on semconv v1.41.0) inside resource.Merge — the fix is to bump grafana/dskit to a version using semconv/v1.43.0, which sweeps in many other unrelated dep bumps and is out of scope for this Renovate PR. The tempodb/wal and e2e-storage failures look like pre-existing timing flakes (uint32 Unix-second boundary comparison and an integration-harness race) unrelated to the grpc-gateway bump.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: grpc-gateway v2.30.0 transitively bumps go.opentelemetry.io/otel/sdk to v1.45.0, whose resource.Default() now uses semconv/v1.43.0, but the pinned github.com/grafana/dskit still calls resource.Merge with semconv/v1.41.0, so pkg/tracing tests fail with "conflicting Schema URL 1.43.0 vs 1.41.0". Next step: bump github.com/grafana/dskit to a commit that uses semconv/v1.43.0 (e.g. v0.0.0-20260824024943-e68091815c4c or newer) alongside this Renovate PR and re-run go mod tidy && go mod vendor.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: grpc-gateway v2.30.0 requires go.opentelemetry.io/otel/sdk v1.45.0 (confirmed via go mod graph), whose resource.Default() now uses semconv v1.43.0's SchemaURL, which conflicts with dskit/tracing.NewResource's v1.41.0 SchemaURL in resource.Merge and breaks pkg/tracing.TestInstallOTelOrJaegerFromEnv*. Human next step: bump grafana/dskit past the semconv v1.41.0→v1.43.0 update (or wait for it) and re-run this Renovate PR — OTel can't be downgraded here without reverting grpc-gateway itself.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: The otel/sdk v1.44.0→v1.45.0 bump switched resource.Default() to semconv/v1.43.0, but vendored github.com/grafana/dskit at v0.0.0-20260703122047 still uses semconv/v1.41.0 in tracing.NewResource, so resource.Merge rejects the schema URL mismatch and every pkg/tracing.TestInstallOTelOrJaegerFromEnv* subtest fails. Next step: bump github.com/grafana/dskit to a revision whose tracing package uses semconv/v1.43.0 (latest works but cascades otel to v1.46 and needs contrib/bridges/otelzap bumped too, so it should be its own PR). The integration TestBackendSchedulerRedaction failure looks unrelated (flaky trace-lookup race) and needs a separate rerun to confirm.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: The grpc-gateway v2.30 bump forces go.opentelemetry.io/otel/sdk to v1.45 (which uses semconv/v1.43.0 in resource.Default), but grafana/dskit's tracing package still builds its resource with semconv/v1.41.0 — so resource.Merge in pkg/tracing fails with 'conflicting Schema URL 1.43.0 and 1.41.0'. Bumping dskit to v0.0.0-20260824024943-e68091815c4c (dskit switched to semconv 1.43 on 2026-08-14) fixes it but expands the PR by ~248 vendored files of transitive updates — a scope call a human should make.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: grpc-gateway/v2 v2.30.0 requires go.opentelemetry.io/otel/sdk v1.45.0, whose resource.Default() now uses semconv v1.43.0, so it conflicts at merge time with grafana/dskit's tracing package (still on semconv v1.41.0) and breaks pkg/tracing.TestInstallOTelOrJaegerFromEnv*; the fix is a coordinated bump of github.com/grafana/dskit to a version using semconv v1.43.0 (e.g. v0.0.0-20260824024943-e68091815c4c), which is out of scope for this Renovate PR.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: The grpc-gateway v2.30.0 bump transitively raised OTel SDK to v1.45, whose resource.Default() now uses semconv/v1.43.0; vendored dskit tracing still hardcodes semconv/v1.41.0 in NewResource, so resource.Merge fails with 'conflicting Schema URL' and breaks every pkg/tracing test. The remaining TestCompactionProvider_EmptyStart failure passed 5x locally and is an unrelated flake. Next step: bump grafana/dskit to a version whose tracing package uses semconv/v1.43.0 (or newer) alongside this Renovate PR.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: grpc-gateway v2.30.0 hard-requires go.opentelemetry.io/otel v1.45.0, whose SDK builtin resource now uses semconv v1.43.0, but the pinned github.com/grafana/dskit still uses v1.41.0 — dskit tracing's resource.Merge(resource.Default(), NewWithAttributes(semconv.SchemaURL,…)) fails with "conflicting Schema URL" and cannot be resolved by adapting tempo code alone. A human needs to bump github.com/grafana/dskit to a version whose tracing package uses semconv v1.43.0 (or add a replace directive to one).