Merging to release-5.13.0: [TT-17154] Bump opentelemetry to post-v0.0.25 doc-comment fixes (#8240)#8250
Merged
Merged
Conversation
## Summary - Bumps `github.com/TykTechnologies/opentelemetry` from `v0.0.25` to `v0.0.26-0.20260521112223-3b0d024e6090`, pulling in [opentelemetry#69](TykTechnologies/opentelemetry#69) (merge commit `3b0d024e`). - That PR is a documentation-only change: it clarifies the config struct comments that drive user-facing OpenTelemetry docs generation (`ExporterConfig.Exporter`, `ResourceName`, `OpenTelemetry.Enabled`, `TLS.Enable`, `TLS.CAFile`). No behavior, API, or default changes. - Pinned via Go pseudo-version because no new tag was cut after `v0.0.25` for this commit. ## Motivation PR review feedback on the gateway-side OpenTelemetry config docs noted unclear/inconsistent wording and grammar issues. Since the docs are generated from the upstream library's struct comments, the fixes live in `TykTechnologies/opentelemetry`. This PR brings those fixes into the gateway. ## Test plan - [x] `go build ./...` — OTel-touching packages (`./internal/otel/...`, `./internal/graphql/...`, `./gateway/...`) compile clean. The only build noise (`test/goplugins` "main undeclared", linker duplicate `-ldl` warning) is pre-existing on master and unrelated. - [x] `go vet ./internal/otel/...` — passes. - [x] `go mod tidy` — clean, no unrelated module churn. - [ ] CI green on this branch. ## Notes for reviewers - Since the upstream change is comment-only, the diff here is minimal (2 lines in `go.mod`, 4 in `go.sum`). - Once a `v0.0.26` tag is cut on the opentelemetry repo, a follow-up can replace the pseudo-version with the clean tag — but functionally identical. <!---TykTechnologies/jira-linter starts here--> ### Ticket Details <details> <summary> <a href="https://tyktech.atlassian.net/browse/TT-17154" title="TT-17154" target="_blank">TT-17154</a> </summary> | | | |---------|----| | Status | In Code Review | | Summary | Gateway API + config 5.13.0 | Generated at: 2026-05-21 11:53:06 </details> <!---TykTechnologies/jira-linter ends here--> (cherry picked from commit 8a9a180)
mativm02
enabled auto-merge (squash)
May 26, 2026 12:02
Contributor
|
This pull request cherry-picks a dependency update for The upstream change in the Files Changed AnalysisThe changes are confined to Go's dependency management files:
Architecture & Impact Assessment
Scope Discovery & Context Expansion
Metadata
Powered by Visor from Probelabs Last updated: 2026-05-28T19:26:55.554Z | Triggered by: pr_updated | Commit: 4831a28 💡 TIP: You can chat with Visor using |
Contributor
✅ Architecture Check PassedNo architecture issues found – changes LGTM. ✅ Performance Check PassedNo performance issues found – changes LGTM. \n\n✅ Architecture Check PassedNo architecture issues found – changes LGTM. \n\n✅ Performance Check PassedNo performance issues found – changes LGTM. \n\n✅ Quality Check PassedNo quality issues found – changes LGTM. Powered by Visor from Probelabs Last updated: 2026-05-28T19:26:29.637Z | Triggered by: pr_updated | Commit: 4831a28 💡 TIP: You can chat with Visor using |
mativm02
added
the
deps-reviewed
2 tasks
mativm02
added a commit
that referenced
this pull request
May 28, 2026
## Summary Re-applies the one-line workflow timeout bump from Ilija's #8156 (commit `edfe152a0`) which is currently regressed on `release-5.13.0`. | Branch | `Run API tests` `timeout-minutes` | |---|---| | `release-5.13` | 40 | | `release-5.13.0` | 30 (regressed) | | `master` | 40 | `edfe152a0` is present in `release-5.13.0`'s history, but later FIPS-related PRs (`9d14d228b` disable FIPS / `1d51bf98d` re-enable FIPS) rewrote the workflow and ended up restoring 30m. ## Evidence api-tests on PR #8250 currently fail with `##[error]The action has timed out.` after exactly 30 minutes. Tests took 32-33min on that run — they would have passed under 40m. ## Test plan - [ ] CI green on this branch - [ ] api-tests step on dependent PRs (#8250 etc) completes without timeout <!---TykTechnologies/jira-linter starts here--> ### Ticket Details <details> <summary> <a href="https://tyktech.atlassian.net/browse/TT-17077" title="TT-17077" target="_blank">TT-17077</a> </summary> | | | |---------|----| | Status | Closed | | Summary | CI/CD: Increase timeout for API tests job | Generated at: 2026-05-28 15:49:07 </details> <!---TykTechnologies/jira-linter ends here-->
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Cherry-pick of #8240 onto
release-5.13.0.Bumps
github.com/TykTechnologies/opentelemetryfromv0.0.25tov0.0.26-0.20260521112223-3b0d024e6090, pulling in doc-comment fixes (TykTechnologies/opentelemetry#69). Documentation-only upstream change — no behavior, API, or default changes.Follow-up to #8235 (the docs update that already landed on
release-5.13.0), bringing the matching gateway-side library bump.go.mod(2 lines),go.sum(4 lines)Test plan
Ticket Details
TT-17154
Generated at: 2026-05-28 19:25:56