Need information on tyk gateway version

anilnp · March 4, 2026, 11:47am

I am currently using tyk-gateway version 5.1.1. What would be the end of life date for this particular version.

I am planning on upgrading to 5.8.10 . Is this a stable version ?
Could see the version in this as “v5.5.0-dev” . Is this intentional ?

github.com

TykTechnologies/tyk/blob/v5.8.10/internal/build/version.go

package build

// These values are injected at build-time from CI.
var (
	// Version contains the tagged gateway version. It may contain a `rc` suffix,
	// which may be delimited with `-rc` or any other suffix. Follows Semver+Tag.
	Version = "v5.5.0-dev"

	// BuiltBy contains the environment name from the build (goreleaser).
	BuiltBy string = "dev"

	// BuildDate is the date the build was made at.
	BuildDate string

	// Commit is the commit hash for the build source.
	Commit string
)

Isaac · March 17, 2026, 10:45am

Hello Anilnp,

Tyk version 5.1.x is a minor (non-LTS) release. Under our release lifecycle policy, minor releases reach their End-of-Life as soon as the next minor version is released. Because Tyk 5.2.0 was released in September 2023, version 5.1.1 is already End-of-Life and no longer receives security patches or updates.

I am planning on upgrading to 5.8.10 . Is this a stable version ?
Yes, Version 5.8.10 is a stable release. this is a patch release in the 5.8.x line, so it primarily contains bug fixes and security patches. You can review the full release notes here for details on what’s included: Tyk Gateway Release Notes - Tyk Documentation

Could see the version in this as “v5.5.0-dev” . Is this intentional ?
The “v5.5.0-dev” you see in the source code on GitHub is just a placeholder value. During the official release build process, Tyk’s CI pipeline injects the correct version number, commit hash, and build date into those variables at compile time. So the actual v5.8.10 binary you’d be running will correctly report itself as v5.8.10. The “dev” default exists so that if someone builds the Gateway directly from source (outside the CI pipeline), the binary clearly identifies itself as a development build rather than an official release.

Do let us know if this helps.

Regards