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):

• 34 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
go.yaml.in/yaml/v3	v3.0.4 -> v3.0.5
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/analysis	v0.25.2 -> v0.25.5
github.com/go-openapi/loads	v0.24.0 -> v0.25.0
github.com/go-openapi/spec	v0.22.5 -> v0.22.9
github.com/go-openapi/strfmt	v0.26.3 -> v0.27.0
github.com/go-openapi/swag	v0.27.1 -> v0.28.0
github.com/go-openapi/swag/cmdutils	v0.27.1 -> v0.28.0
github.com/go-openapi/swag/conv	v0.27.1 -> v0.28.0
github.com/go-openapi/swag/fileutils	v0.27.1 -> v0.28.0
github.com/go-openapi/swag/jsonutils	v0.27.1 -> v0.28.0
github.com/go-openapi/swag/loading	v0.27.1 -> v0.28.0
github.com/go-openapi/swag/mangling	v0.27.1 -> v0.28.0
github.com/go-openapi/swag/netutils	v0.27.1 -> v0.28.0
github.com/go-openapi/swag/pools	v0.27.1 -> v0.28.0
github.com/go-openapi/swag/stringutils	v0.27.1 -> v0.28.0
github.com/go-openapi/swag/typeutils	v0.27.1 -> v0.28.0
github.com/go-openapi/swag/yamlutils	v0.27.1 -> v0.28.0
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/sdk to v1.45.0, whose resource.Default() now uses semconv/v1.43.0, while vendored grafana/dskit tracing/otel.go still merges against semconv/v1.41.0, so resource.Merge returns ErrSchemaURLConflict and every TestInstallOTelOrJaegerFromEnv* case fails at pkg/tracing/tracing.go via dstracing.NewOTelOrJaegerFromEnv. Fix needs a dskit release that upgrades to semconv/v1.43.0 (current dskit main still uses v1.41.0) or a replace directive pinning OTel to v1.44.0 — both out of scope for a Renovate PR.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: The grpc-gateway v2.30.0 bump transitively pulls otel v1.45.0, whose sdk resource.Default() now uses semconv/v1.43.0, which conflicts with github.com/grafana/dskit/tracing.NewResource still importing semconv/v1.41.0 as the schema URL — the fix has to land in dskit (bump it to a version that uses semconv/v1.43.0) and cannot be made from the tempo side.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: The pkg/tracing failures come from OTel 1.44→1.45 being pulled in transitively by go mod tidy: OTel SDK 1.45's resource.Default() now carries semconv/v1.43.0, but grafana/dskit's tracing.NewResource still merges with semconv/v1.41.0, and resource.Merge treats mismatched schema URLs as fatal — so the fix belongs in dskit (bump its semconv) or in a separate PR that pins OTel back to 1.44; the redaction integration test failure is unrelated and looks flaky. Next step for a human: bump grafana/dskit to a version whose tracing package uses semconv v1.43.0, or pin go.opentelemetry.io/otel* back to v1.44.0 in go.mod.