Merging to release-5.8: Tt 16178 update gateway to kinopenapi fork (#7594)

[probelabs]

User description

Cherry-pick of 7169c3a3983913d7f0c4d7127a6f1ee983c60730 from master to release-5.8 requires manual resolution.

Conflicts detected: 6

• go.mod
• go.sum

Tips:

• Check out this branch locally and run: git cherry-pick -x 7169c3a3983913d7f0c4d7127a6f1ee983c60730
• Resolve conflicts (including submodules if any), then push back to this branch.

Original commit: 7169c3a

---

PR Type

Enhancement, Other

---

Description

• Replace kin-openapi with Tyk fork

• Pin fork to version v0.92.0

• Maintain otelhttp replace constraint

---

Diagram Walkthrough

flowchart LR
  A["go.mod dependency map"] -- "replace getkin/kin-openapi" --> B["TykTechnologies/kin-openapi v0.92.0"]
  A -- "keep" --> C["otelhttp replace v0.49.0"]

Loading

File Walkthrough

	Relevant files
Enhancement	go.mod Point kin-openapi to Tyk fork                                                        go.mod Replace github.com/getkin/kin-openapi with github.com/TykTechnologies/kin-openapi. Pin forked dependency to v0.92.0. Preserve existing otelhttp replace directive. +1/-1

---

[github-actions]

PR Reviewer Guide 🔍

(Review updated until commit ddfac34)

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Dependency Pin Validate that replacing github.com/getkin/kin-openapi with github.com/TykTechnologies/kin-openapi v0.92.0 is compatible with all existing imports and transitive dependencies, and that module proxies/CI can fetch the forked module reliably. replace github.com/getkin/kin-openapi => github.com/TykTechnologies/kin-openapi v0.92.0 Version Consistency Confirm that the pinned fork version v0.92.0 matches the APIs expected by the codebase and any generators/tools relying on kin-openapi, especially across release branches. replace github.com/getkin/kin-openapi => github.com/TykTechnologies/kin-openapi v0.92.0

[github-actions]

PR Code Suggestions ✨

Latest suggestions up to ddfac34
Explore these optional code suggestions:

Category	Suggestion	Impact
General	Narrow the replace scope Constrain the replace directive to the specific module path(s) used (e.g., submodules like openapi3) to avoid unintentionally overriding all transitive usages. This reduces the risk of incompatible API substitutions across dependencies. go.mod [333] -replace github.com/getkin/kin-openapi => github.com/TykTechnologies/kin-openapi v0.92.0 +replace github.com/getkin/kin-openapi/openapi3 => github.com/TykTechnologies/kin-openapi/openapi3 v0.92.0 Suggestion importance[1-10]: 4 __ Why: The existing code matches a new hunk line and the suggestion to narrow the replace can reduce unintended overrides, but it may break builds if other subpackages are used and lacks confirmation that only openapi3 is needed. The impact is modest and context-dependent.	Low

---

Previous suggestions

Suggestions up to commit ddfac34

Category	Suggestion	Impact
Possible issue	Ensure correct module versioning Pin the replace to the exact upstream module path version to avoid accidental transitive mismatches. Also include the original module's major version suffix if applicable to ensure Go's MVS resolves correctly. go.mod [333] -replace github.com/getkin/kin-openapi => github.com/TykTechnologies/kin-openapi v0.92.0 +replace github.com/getkin/kin-openapi => github.com/TykTechnologies/kin-openapi v0.92.0+incompatible Suggestion importance[1-10]: 3 __ Why: The suggestion to append '+incompatible' is speculative without evidence that the target module lacks a go.mod or uses a different module path; Go tooling adds this automatically when needed. Low impact and uncertain correctness relative to the diff.	Low

[github-actions]

🚨 Jira Linter Failed

Commit: ddfac34
Failed at: 2025-12-08 08:54:02 UTC

The Jira linter failed to validate your PR. Please check the error details below:

🔍 Click to view error details

failed to validate branch and PR title rules: branch name 'merge/release-5.8/7169c3a3983913d7f0c4d7127a6f1ee983c60730' must contain a valid Jira ticket ID (e.g., ABC-123)

Next Steps

• Ensure your branch name contains a valid Jira ticket ID (e.g., ABC-123)
• Verify your PR title matches the branch's Jira ticket ID
• Check that the Jira ticket exists and is accessible

---

This comment will be automatically deleted once the linter passes.

[github-actions]

Persistent review updated to latest commit ddfac34

[github-actions]

API Changes

no api changes detected

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud