Tyk Gateway v5.6.1, Tyk Dashboard v5.6.1

Tyk Gateway 5.6.1

• Fixed critical stability issues for users running Tyk Gateway within the data
  plane, connecting to the control plane or Tyk Hybrid. Affected users should upgrade immediately to version 5.6.1 to
  avoid service interruptions and ensure reliable operations with the control plane or Tyk Hybrid.

Tyk Dashboard 5.6.1

• Version alignment (no code changes)

Tyk Gateway v5.3.7, Tyk Dashboard v5.3.7

Tyk Gateway 5.3.7

• Fixed critical stability issues for users running Tyk Gateway within the data
  plane, connecting to the control plane or Tyk Hybrid. Affected users should upgrade immediately to version 5.6.1 to
  avoid service interruptions and ensure reliable operations with the control plane or Tyk Hybrid.

Tyk Dashboard 5.3.7

• Version alignment (no code changes)

v5.3.7-rc3

Merging to release-5.3.7: TT-13130 update gorpc version (#6644)

TT-13130 update gorpc version (#6644)

### **User description**
<details open>
<summary><a href="https://tyktech.atlassian.net/browse/TT-13130"
title="TT-13130" target="_blank">TT-13130</a></summary>
  <br />
  <table>
    <tr>
      <th>Summary</th>
<td>Tyk Cloud: Panic appears when a user tried to deploy GW before
Control Plane is in deployed state </td>
    </tr>
    <tr>
      <th>Type</th>
      <td>
<img alt="Bug"
src="https://tyktech.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium"
/>
        Bug
      </td>
    </tr>
    <tr>
      <th>Status</th>
      <td>In Dev</td>
    </tr>
    <tr>
      <th>Points</th>
      <td>N/A</td>
    </tr>
    <tr>
      <th>Labels</th>
<td><a
href="https://tyktech.atlassian.net/issues?jql=project%20%3D%20TT%20AND%20labels%20%3D%20Re_open%20ORDER%20BY%20created%20DESC"
title="Re_open">Re_open</a>, <a
href="https://tyktech.atlassian.net/issues?jql=project%20%3D%20TT%20AND%20labels%20%3D%20QA_Fail%20ORDER%20BY%20created%20DESC"
title="QA_Fail">QA_Fail</a></td>
    </tr>
  </table>
</details>
<!--
  do not remove this marker as it will break jira-lint's functionality.
  added_by_jira_lint
-->

---

<!-- Provide a general summary of your changes in the Title above -->

## Description

<!-- Describe your changes in detail -->

## Related Issue

TT-13130

## Motivation and Context

<!-- Why is this change required? What problem does it solve? -->

## How This Has Been Tested

<!-- Please describe in detail how you tested your changes -->
<!-- Include details of your testing environment, and the tests -->
<!-- you ran to see how your change affects other areas of the code,
etc. -->
<!-- This information is helpful for reviewers and QA. -->

## Screenshots (if appropriate)

## Types of changes

<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Refactoring or add test (improvements in base code or adds test
coverage to functionality)

## Checklist

<!-- Go over all the following points, and put an `x` in all the boxes
that apply -->
<!-- If there are no documentation updates required, mark the item as
checked. -->
<!-- Raise up any additional concerns not covered by the checklist. -->

- [ ] I ensured that the documentation is up to date
- [ ] I explained why this PR updates go.mod in detail with reasoning
why it's required
- [ ] I would like a code coverage CI quality gate exception and have
explained why


___

### **PR Type**
Bug fix, Enhancement


___

### **Description**
- Updated the `gorpc` library to a newer version in `go.mod` and
`go.sum`.
- Modified the RPC client connection handling by replacing
`ConnectionDialingWG.Wait()` with `WaitForConnection()`, improving the
connection logic.



___



### **Changes walkthrough** 📝
<table><thead><tr><th></th><th align="left">Relevant
files</th></tr></thead><tbody><tr><td><strong>Enhancement</strong></td><td><table>
<tr>
  <td>
    <details>
<summary><strong>rpc_client.go</strong><dd><code>Update connection
handling in RPC client</code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; </dd></summary>
<hr>

rpc/rpc_client.go

<li>Replaced <code>ConnectionDialingWG.Wait()</code> with
<code>WaitForConnection()</code>.<br> <li> Improved connection handling
logic.<br>


</details>


  </td>
<td><a
href="https://github.com/TykTechnologies/tyk/pull/6644/files#diff-3b88914c99bb9418e44e6389ce73579843562e8900730b380d7fff2e95c51033">+1/-1</a>&nbsp;
&nbsp; &nbsp; </td>

</tr>                    
</table></td></tr><tr><td><strong>Dependencies</strong></td><td><table>
<tr>
  <td>
    <details>
<summary><strong>go.mod</strong><dd><code>Update gorpc dependency
version in go.mod</code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
</dd></summary>
<hr>

go.mod

- Updated `gorpc` dependency version.



</details>


  </td>
<td><a
href="https://github.com/TykTechnologies/tyk/pull/6644/files#diff-33ef32bf6c23acb95f5902d7097b7a1d5128ca061167ec0716715b0b9eeaa5f6">+1/-1</a>&nbsp;
&nbsp; &nbsp; </td>

</tr>                    

<tr>
  <td>
    <details>
<summary><strong>go.sum</strong><dd><code>Update go.sum with new gorpc
checksums</code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; </dd></summary>
<hr>

go.sum

- Added new checksum entries for updated `gorpc` version.



</details>


  </td>
<td><a
href="https://github.com/TykTechnologies/tyk/pull/6644/files#diff-3295df7234525439d778f1b282d146a4f1ff6b415248aaac074e8042d9f42d63">+2/-0</a>&nbsp;
&nbsp; &nbsp; </td>

</tr>                    
</table></td></tr></tr></tbody></table>

___

> 💡 **PR-Agent usage**: Comment `/help "your question"` on any pull
request to receive relevant information

---------

Co-authored-by: sredny buitrago <[email protected]>

v5.7.0-alpha2

Fix response body detailed recording

v5.8.0-alpha2

Add support for websocket rate limiting

Should be enabled with `enable_websockets_rate_limiting`

v5.8.0-alpha1

Add support for bi-directional websockets and http endpoints

Now you can different inputs and outputs can point to the same endpoints. But
only one input and one output per each endpoint.

Tyk Gateway v5.6.0, Tyk Dashboard v5.6.0

Tyk Gateway 5.6.0

Release notes:

https://tyk.io/docs/product-stack/tyk-dashboard/release-notes/version-5.6/

Tyk Dashboard 5.6.0

Release notes:

https://tyk.io/docs/product-stack/tyk-dashboard/release-notes/version-5.6/

Tyk Gateway v5.5.2, Tyk Dashboard v5.5.2

Tyk Gateway 5.5.2

• This release replaces Tyk Gateway 5.5.1 which was accidentally released as a non-distroless image, which re-introduced some CVEs like CVE-2023-45853.

Tyk Dashboard 5.5.2

This release replaces Tyk Gateway 5.5.1 which was accidentally released as a non-distroless image, which re-introduced some CVEs like CVE-2023-45853.

Tyk Gateway v5.3.6, Tyk Dashboard v5.3.6

Tyk Gateway 5.3.6

Release Notes

https://tyk.io/docs/product-stack/tyk-gateway/release-notes/version-5.3/

Tyk Dashboard 5.3.6

Release Notes

https://tyk.io/docs/product-stack/tyk-dashboard/release-notes/version-5.3/

Tyk Gateway v5.3.5, Tyk Dashboard v5.3.5

Tyk Gateway 5.3.5

Fixed

• We have introduced two new options in the Gateway configuration that will enforce prefix and/or suffix matching when Tyk performs checks on whether middleware or other logic should be applied to a request.
  enable_path_prefix_matching ensures that the start of the request path must match the path defined in the API definition
  enable_path_suffix_matching ensures that the end of the request path must match the path defined in the API definition
  combining enable_path_prefix_matching and enable_path_suffix_matching will ensure an exact (explicit) match is performed
  These configuration options provide control to avoid unintended matching of paths from Tyk's default wildcard match. Use of regex special characters when declaring the endpoint path in the API definition will automatically override these settings for that endpoint.
  Tyk recommends that exact matching is employed, but both options default to false to avoid introducing a breaking change for existing users.
• Fixed an issue when using granular Path-Based Permissions in access policies and keys that led to authorization incorrectly being granted to endpoints if an invalid regular expression was configured in the key/policy. Also fixed an issue where path-based parameters were not correctly handled by Path-Based Permissions. Now Tyk's authorization check correctly handles both of these scenarios granting access only to the expected resources.
• Fixed an issue where a parameterized endpoint URL (e.g. /user/{id}) would be invoked if a request is made that omits the parameter. For example, a request to /user/ will now be interpreted as a request to /user and not to /user/{id}.
• Enhanced Tyk Gateway synchronization with MDCB to ensure reliable policy and API loading. Implemented synchronous initialization process to prevent startup failures and potential service disruptions.

Tyk Dashboard 5.3.5

• Version alignment (no code changes)