Skip to content

[DX-1942] Tyk Sync Release Notes 2.1.1 #6291

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 5 commits into
base: master
Choose a base branch
from
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 38 additions & 0 deletions tyk-docs/content/developer-support/release-notes/sync.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,44 @@ Our minor releases are supported until our next minor comes out.

## 2.1 Release Notes

### 2.1.1 Release Notes

#### Release Date XXX

#### Release Highlights

This release focuses mainly on bug fixes. Please refer to the [changelog]({{< ref "#Changelog-v2.1.1">}}) below for detailed explanation.

#### Breaking Changes

This release has no breaking changes.

#### Deprecations
There are no deprecations in this release.

#### Upgrade instructions
For users currently on v2.0.0, we strongly recommend promptly upgrading to the latest release. If you are working with an older version (lower major), it is advisable to bypass version 2.0.0 and proceed directly to this latest patch release.
<br/>
Go to the [Upgrading Tyk](#upgrading-tyk) section for detailed upgrade Instructions.

#### Downloads
- [Docker image v2.1.1](https://hub.docker.com/r/tykio/tyk-sync/tags?page=&page_size=&ordering=-name&name=v2.1.1)
- ```bash
docker pull tykio/tyk-sync:v2.1.1
```

#### Changelog {#Changelog-v2.1.1}

<ul>
<li>
<details>
<summary>Fixed incorrect API-level rate limits from dump command</summary>

Fixed an issue where the dump command could incorrectly set API-level rate limits in a policy that did not set such limits. This was due to an issue with Sync interpreting the default value if no limit is set in the policy. Now Sync respects the original policy if no API-level rate limit is set.
</details>
</li>
</ul>

### 2.1.0 Release Notes

#### Release Date 28 March 2025
Expand Down
Loading