Support Lifetime
Our minor releases are supported until our next minor comes out.1.13 Release Notes
1.13.0 Release Notes
Release Date 29 October 2025
Breaking Changes
This release has no breaking changes, but does include the deprecation of two global configuration options (DecodeRawRequest and DecodeRawResponse) that did not previously work. There is no change to functionality from these deprecations.Dependencies
3rd Party Dependencies & Tools
| Third Party Dependency | Tested Versions | Compatible Versions |
|---|---|---|
| MongoDB | 5.x, 6.x, and 7.0 | 4.4.x, 5.x, 6.x, and 7.0 |
| PostgreSQL | 13.x - 17.x | 13.x - 17.x |
| Redis | 6.x - 7.0 | 6.x - 7.x |
| Valkey | 8.0.x, 8.1.x | 7.2.x, 8.0.x, 8.1.x |
Deprecations
Deprecated the global configuration options DecodeRawRequest and DecodeRawResponse. For further information, please check the changelog below.Upgrade instructions
For users currently on v1.12.2, 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 1.12.2 and proceed directly to this latest patch release.Go to the Upgrading Tyk section for detailed upgrade Instructions.
Downloads
- Docker Image v1.13.0
-
- Source code tarball for OSS - GH Tyk Pump Repo
Changelog
Changed
Added
Added support for encrypted Kinesis streams in Pump
Added support for server-side encryption in the Kinesis Pump by introducing a new configuration option TYK_PMP_PUMPS_KINESIS_META_KMSKEYID that allows users to specify an AWS KMS key for encrypting data at rest in Kinesis Data Streams.This enhancement enables compliance with strict regulatory requirements and security needs by automatically encrypting data before it’s written to Kinesis storage and decrypting it when retrieved. The feature is backward compatible, with server-side encryption disabled by default for existing deployments.Added "Latency.Total" and "Latency.Upstream" fields to InfluxDB2 Pump
Added two new fields to the traffic logs transferred using the InfluxDB2 pump.Latency.Total: Represents the total time taken to process a request.Latency.Upstream: Represents the time taken to communicate with the upstream.
Latency.Total-Latency.Upstream), which is essential for monitoring API performance and diagnosing bottlenecks. This enhancement enables customers to perform comprehensive latency analysis and identify performance bottlenecks in their API infrastructure.Added "batchbytes" configuration option for Kafka pump
Added a new configuration option TYK_PMP_PUMPS_KAFKA_META_BATCHBYTES to the Kafka pump that allows users to configure the maximum size (in bytes) of a batch before it is sent to a Kafka partition.This enhancement resolves issues where batched analytics data exceeded Kafka’s default 1MB message size limit, causing “Message Size Too Large” errors and resulting in missing analytics data. Users can now optimize the batch size to match their Kafka topic configurations, with backward compatibility maintained through the default 1MB limit.
1.12 Release Notes
1.12.1 Release Notes
Release Date 18 August 2025
Release Highlights
This release improves log reliability in the Syslog Pump by ensuring that raw request and response data are no longer fragmented into multiple entries. Logs are now consolidated into a single entry per API request, making analysis easier while preserving compatibility with existing log parsers. For a comprehensive list of changes, please refer to the detailed changelog below.Breaking Changes
This release has no breaking changesDependencies
3rd Party Dependencies & Tools
| Third Party Dependency | Tested Versions | Compatible Versions | Comments |
|---|---|---|---|
| MongoDB | 5.x, 6.x, and 7.0 | 4.4.x, 5.x, 6.x, and 7.0 | Used by Tyk Pump and Tyk Dashboard |
| PostgreSQL | 13.x - 17.x | 13.x - 17.x | Used by Tyk Pump and Tyk Dashboard |
| Redis | 6.x - 7.0 | 6.x - 7.x | Used by all Tyk components |
Deprecations
There are no deprecations in this release.Upgrade instructions
For users currently on v1.12.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 1.12.0 and proceed directly to this latest patch release.Go to the Upgrading Tyk section for detailed upgrade Instructions.
Downloads
- Docker Image v1.12.1
-
- Source code tarball for OSS - GH Tyk Pump Repo
Changelog
Fixed
1.12.0 Release Notes
Release Date 28 March 2025
Release Highlights
This release enhances Pump’s database compatibility and security by adding support for PostgreSQL 17, removing SQLite support, and addressing critical security vulnerabilities (CVEs). These improvements ensure better performance, long-term stability, and overall enhanced security. For a comprehensive list of changes, please refer to the detailed changelog below.Breaking Changes
This release removes support for SQLite in Pump, aligning with the broader removal of SQLite from the Tyk Dashboard. This change improves compatibility with enterprise environments and addresses implementation issues related to SQLite.Dependencies
3rd Party Dependencies & Tools
With PostgreSQL v11 reaching EOL in November 2023, we can no longer guarantee full compatibility with this version of the database. If you are using PostgreSQL we recommend that you upgrade to a version that we have tested with, as indicated below.| Third Party Dependency | Tested Versions | Compatible Versions | Comments |
|---|---|---|---|
| MongoDB | 5.x, 6.x, and 7.0 | 4.4.x, 5.x, 6.x, and 7.0 | Used by Tyk Pump and Tyk Dashboard |
| PostgreSQL | 13.x - 17.x | 13.x - 17.x | Used by Tyk Pump and Tyk Dashboard |
| Redis | 6.x - 7.0 | 6.x - 7.x | Used by all Tyk components |
Deprecations
There are no deprecations in this release.Upgrade instructions
For users currently on v1.11.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 1.11.0 and proceed directly to this latest patch release.Go to the Upgrading Tyk section for detailed upgrade Instructions.
Downloads
- Docker Image v1.12.0
-
- Source code tarball for OSS - GH Tyk Pump Repo
Changelog
Changed
Security Fixes
1.11 Release Notes
1.11.2 Release Notes
Release Date 10 January 2025
Release Highlights
This patch release focuses on improving the robustness of SQL-Pump in scenarios involving table sharding and analytics data, ensuring smoother operations and better compatibility with PostgreSQL-based environments.Breaking Changes
This release has no breaking changes.Dependencies
3rd Party Dependencies & Tools
With PostgreSQL v11 reaching EOL in November 2023, we can no longer guarantee full compatibility with this version of the database. If you are using PostgreSQL we recommend that you upgrade to a version that we have tested with, as indicated below.| Third Party Dependency | Tested Versions | Compatible Versions | Comments |
|---|---|---|---|
| MongoDB | 5.x, 6.x, and 7.0 | 4.4.x, 5.x, 6.x, and 7.0 | Used by Tyk Pump and Tyk Dashboard |
| PostgreSQL | 12.x - 16.x | 12.x - 16.x | Used by Tyk Pump and Tyk Dashboard |
| Redis | 6.x - 7.0 | 6.x - 7.x | Used by all Tyk components |
Deprecations
There are no deprecations in this release.Upgrade instructions
For users currently on v1.11.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 1.11.0 and proceed directly to this latest patch release.Go to the Upgrading Tyk section for detailed upgrade Instructions.
Downloads
- Docker Image v1.11.2
-
- Source code tarball for OSS - GH Tyk Pump Repo
Changelog
Fixed
1.11.1 Release Notes
Release Date 04 December 2024
Release Highlights
This patch release focuses on critical dependency updates to address security vulnerabilities and maintain compatibility with the latest tools. Users are encouraged to upgrade to benefit from enhanced security and improved stability.Breaking Changes
This release has no breaking changes.Dependencies
3rd Party Dependencies & Tools
With PostgreSQL v11 reaching EOL in November 2023, we can no longer guarantee full compatibility with this version of the database. If you are using PostgreSQL we recommend that you upgrade to a version that we have tested with, as indicated below.| Third Party Dependency | Tested Versions | Compatible Versions | Comments |
|---|---|---|---|
| MongoDB | 5.x, 6.x, and 7.0 | 4.4.x, 5.x, 6.x, and 7.0 | Used by Tyk Dashboard |
| PostgreSQL | 12.x - 16.x | 12.x - 16.x | Used by Tyk Dashboard |
| Redis | 6.x - 7.0 | 6.x - 7.x | Used by all Tyk components |
Deprecations
There are no deprecations in this release.Upgrade instructions
For users currently on v1.11.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 1.11.0 and proceed directly to this latest patch release.Go to the Upgrading Tyk section for detailed upgrade Instructions.
Downloads
- Docker Image v1.11.1
-
- Source code tarball for OSS - GH Tyk Pump Repo
Changelog
Changed
Security Fixes
- Fixed the following CVEs:
1.11.0 Release Notes
Release Date 13 August 2024
Breaking Changes
This release has no breaking changes.Dependencies
3rd Party Dependencies & Tools
With PostgreSQL v11 reaching EOL in November 2023, we can no longer guarantee full compatibility with this version of the database. If you are using PostgreSQL we recommend that you upgrade to a version that we have tested with, as indicated below.| Third Party Dependency | Tested Versions | Compatible Versions | Comments |
|---|---|---|---|
| GoLang | 1.19, 1.20, 1.21 | 1.19, 1.20, 1.21 | All our binaries |
| MongoDB | 5.x, 6.x, and 7.0 | 4.4.x, 5.x, 6.x, and 7.0 | Used by Tyk Dashboard |
| PostgreSQL | 12.x - 16.x | 12.x - 16.x | Used by Tyk Dashboard |
| Redis | 6.x - 7.0 | 6.x - 7.x | Used by all Tyk components |
Deprecations
There are no deprecations in this release.Upgrade instructions
For users currently on v1.10.X, we strongly recommend promptly upgrading to the latest release. If you are working with an older version, it is advisable to bypass version 1.10 and proceed directly to this latest release.Release Highlights
Security fixes
This release focuses on improving security and compliance, enhancing integration capabilities, and ensuring robust performance in secure environments.Downloads
- Docker Image v1.11.0
-
- Source code tarball for OSS - GH Tyk Pump Repo
Changelog
Added
1.10 Release Notes
Release Date 3 July 2024
Breaking Changes
This release has no breaking changes.Dependencies
3rd Party Dependencies & Tools
With PostgreSQL v11 reaching EOL in November 2023, we can no longer guarantee full compatibility with this version of the database. If you are using PostgreSQL we recommend that you upgrade to a version that we have tested with, as indicated below.| Third Party Dependency | Tested Versions | Compatible Versions | Comments |
|---|---|---|---|
| GoLang | 1.19, 1.20, 1.21 | 1.19, 1.20, 1.21 | All our binaries |
| MongoDB | 5.x, 6.x, and 7.0 | 4.4.x, 5.x, 6.x, and 7.0 | Used by Tyk Dashboard |
| PostgreSQL | 12.x - 16.x | 12.x - 16.x | Used by Tyk Dashboard |
| Redis | 6.x - 7.0 | 6.x - 7.x | Used by all Tyk components |
Deprecations
There are no deprecations in this release.Upgrade instructions
For users currently on v1.9.X, we strongly recommend promptly upgrading to the latest release. If you are working with an older version, it is advisable to bypass version 1.9 and proceed directly to this latest release.Release Highlights
FIPS Compliance
Tyk Pump now offers FIPS 140-2 compliance. For further details please consult Tyk API Management FIPS supportSecurity fixes
This release focuses on improving security and compliance, enhancing integration capabilities, and ensuring robust performance in secure environments.Downloads
- Docker Image v1.10.0
-
- Source code tarball for OSS - GH Tyk Pump Repo
Changelog
Added
Fixed
Security Fixes
1.9 Release Notes
Release Date 5 Apr 2024
Breaking Changes
Attention: Please read this section carefully
MongoDB v4.4 will reach its end of life support at the end of February 2024. In order to support newer versions of MongoDB and align with newer versions of Tyk, we have changed the default MongoDB driver from mgo to mongo-go. Themongo-go driver supports MongoDB versions greater or equal to v4. If you are using a version of MongoDB less than v4, please follow this guide to update the driver type to mgo.
Users are strongly advised to follow the recommended upgrade instructions provided by Tyk before applying any updates.
Dependencies
3rd Party Dependencies & Tools
| Third Party Dependency | Tested Versions | Compatible Versions | Comments |
|---|---|---|---|
| GoLang | 1.19, 1.20, 1.21 | 1.19, 1.20, 1.21 | All our binaries |
| MongoDB | 5.x, 6.x, and 7.0 | 4.4.x, 5.x, 6.x, and 7.0 | Used by Tyk Dashboard |
| PostgreSQL | 11.x - 15.x LTS | 11.x - 15.x | Used by Tyk Dashboard |
| Redis | 6.x - 7.0 | 6.x - 7.x | Used by all Tyk components |
Deprecations
There are no deprecations in this release.Upgrade instructions
For users currently on v1.8.X, we strongly recommend promptly upgrading to the latest release. If you are working with an older version, it is advisable to bypass version 1.8 and proceed directly to this latest release.Release Highlights
Redis 7 and storage library
Tyk Pump now supports Redis v7, utilizing our storage library v1.2.0.MongoDB Driver
As of v1.9, the default MongoDB driver has been changed frommgo to mongo-go.
AWS Simple Queue Service Support
Thanks to a community contribution by masoudhaghbin, Tyk Pump can now pump logs to an AWS SQS instance.Tyk Graph Pump
There has been a significant enhancement in Tyk Graph Pump with the removal of the dependency on theenable_detailed_recording setting. This change is designed to streamline operations, reduce storage requirements and enhance overall performance in production environments. By decoupling detailed recording from specific configuration options, Tyk Graph Pump now provides greater flexibility and control over data storage.
Downloads
- Docker Image v1.9.0
-
- Source code tarball for OSS - GH Tyk Pump Repo
Changelog
Added
Changed
Fixed
Added backoff retry mechanism for Splunk Pump
Tyk Pump now has an expontential backoff retry mechanism for sending logs to Splunk. This mechanism mitigates the chance of losing logs if Pump should fail to send logs to Splunk. This fixes a bug where Splunk responses were not being checked correctly and fixes a bug where Pump was not closing connections after receiving responses.Added a field so that GraphQL aggregated analytics will display correctly for SQL databases
For SQL databases, the GraphQL aggregated analytics record will now have a newapi_valuefield so that analytics will be shown in the Dashboard correctly.Environment variables TYK_PMP_PUMPS_AGGREGATE_* now correctly correspond to definitions in pump.conf
Fixed a bug where anyTYK_PMP_PUMPS_AGGREGATE_*environment variables didn’t correctly correspond to definitions in the pump.conf file.Added an api_id field so that GraphQL aggregated analytics will display correctly
For SQL databases, the GraphQL aggregated analytics record will now have a newapi_idfield so that analytics will be shown in the Dashboard correctly.Fixed a bug where Tyk Pump could not connect to Redis Sentinel when TLS is enabled
Fixed a bug causing Tyk Pump not to connect when Redis Sentinel was deployed using TLS.
Security Fixes
Community Contributions
Special thanks to the following members of the Tyk community for their contributions to this release:1.8 Release Notes
1.8.3 Release Notes
Changelog
Fixed
- Corrected configuration for pumps.kafka.meta.timeout to be interpreted as the number of seconds (Type: int) instead of a duration requiring a unit (Type: Duration).
- Fixed an issue where Graph SQL Pump couldn’t restart correctly when analytics storage table name was changed in Pump config. Some relations were not torn down and migrated correctly.
1.8.2 Release Notes
Changelog
Fixed
- Resolved performance issue where SQL Aggregate analytics failed to load on the Dashboard during heavy traffic by introducing a new index on the sql_aggregate Pump called idx_dimension.
- Fixed Prometheus Pump crashes on non UTF-8 URLs by updating to prometheus-client v1.16.
- Fixed MongoDB connection string issues related to certain characters (”?” and ”@”), recommending URL-encoded values in usernames and passwords. This ensures compatibility with both mgo and mongo-go drivers.
- Fixed security vulnerabilities: CVE-2022-36640, CVE-2022-21698, GO-2022-0322 and GHSA-cg3q-j54f-5p7p.
Added
- Add
track_all_pathsconfiguration for Prometheus Pump. If enabled, all APIs will have path in thetyk_http_status_per_pathmetric. Otherwise, only endpoint that have “track” plugin set with have path shown in the metric. Endpoints without “track” plugin set will have “unknown” path shown in the metric.
Updated
- Improved security by obfuscating Mongo Pump credentials in log outputs.
1.8.1 Release Notes
Notes on MongoDB v5 and v6 compatibility
For MongoDB v5 and v6 users, please set mongo driver type tomongo-go.From pump v1.8.1, the default MongoDB driver it uses is mgo. This is to align with the default MongoDB driver of other Tyk components. This driver supports MongoDB versions up to v4. If you are using a later version of MongoDB v5 or MongoDB v6, please follow this guide to update the driver type to mongo-go.Changelog
Fixed
- GraphQL analytics records were being excluded from the tyk_analytics collection for Mongo Pump. This has been fixed so that GraphQL analytic records are now included as expected.
- Fixed MongoDB connection issue when using a password with URL escape characters (with mongo-go driver)
- Fixed an issue in Prometheus pump when filtering fields , e.g. API Name, that contain
--in their value. For example,test--name. Prometheus Pump filtered the field as two separate instances, e.g.test&name, instead of the expectedtest--name. - When
omit_configfileis set totrue, Pump will not try to load the config file and spit out error logs
Updated
- Updated the default Hybrid Pump RPC pool size from 20 to 5 connections in order to reduce default CPU and memory footprint. See Pump configurations
- Import and use latest storage library v1.0.5
- Updated default MongoDB driver to
mgo. Follow this guide to update the driver type - Pump name is now case-insensitive. It will override two or more pumps with the same name but in different cases (e.g. Mongo / mongo)
1.8.0 Release Notes
Release date: 2023-05-04Major features
Pump 1.8 introduces two new pumps: The GraphQL SQL Aggregate Pump - which allows you to transfer GraphQL transaction logs to SQL; and Resurface Pump - which allows you to transfer data to Resurface.io for context based security analysis. We have changed the default MongoDB driver from mgo to mongo-go. The new driver supports MongoDB versions greater or equal to v4. If you are using older version of MongoDB v3.x, please follow this guide to update the driver type. We have also added a config option that allow you to decode the raw requests and responses for all pumps so you don’t need to worry about processing them in your data pipeline. For demo mode, there is now an option to generate future data for your convenience. In this release, we are using a new Tyk storage library to connect to Mongo DB. This would allow us to switch to use the official Mongo Driver very easily in the future.Notes on MongoDB v3.x compatibility
In 1.8.0, the default MongoDB driver it use is mongo-go. This driver supports MongoDB versions greater or equal to v4. If you are using older version of MongoDB v3.x, please follow this guide to update the driver type.Changelog
Added
- Added GraphQL SQL Aggregate Pump.
- Added Resurface Pump - Resurface can provide context-based security analysis for attack and failure triage, root cause, threat and risk identification based on detailed API logs sent from Tyk Pump.
- Add config option raw_request_decoded and raw_response_decoded for decoding from base64 the raw requests/responses fields before writing to Pump. This is useful if you want to search for specific values in the raw request/response. Both are disabled by default. This setting is not available for Mongo and SQL pumps, since the dashboard will decode the raw request/response.
- Add the ability to generate future data in demo mode using —demo-future-data flag.
- Remove critical CVE go.uuid vulnerability
- Use the latest Tyk storage library to connect to Mongo
- Hybrid Pump refactoring - we now have better RPC connection control, testability, and documentation
Fixed
- Std pump does not log accurate time when set to json format
- GraphPump doesn’t include names of queries/mutation and subscriptions called
- Mongo Pump’s connection hangs forever if misconfigured