18.10.7 not present in Github Releases section

[uedvt359]

Looking at https://github.com/gravitational/teleport/releases, the latest release looks to be 18.10.0 but https://goteleport.com/docs/changelog/ already lists 18.10.7 as the latest and so do the git tags in this repository. (.1 to .6 are apparently binary-only releases, but .7 is AFAICT a regular one)

Is the GH releases page no longer maintained? If so, is there an RSS feed (or other API) that can be used to monitor for new releases?

[sambai-dev]

The Releases page is genuinely stale: the newest published release object is v18.10.0 (2026-07-09). Everything after it exists as git tags (v18.10.1, v18.10.3, v18.10.6, v18.10.7, v17.7.27, v17.7.28, and now v18.11.0) but has no matching GitHub Release. Requests to the releases-by-tag API return 404 for each one I checked (v18.10.6, v18.10.7, v17.7.27, v17.7.28, v18.11.0), and the releases listing tops out at v18.10.0 / v17.7.26. So this is not a client or cache problem on your side.

Two refinements to the premise:

1. Per the docs changelog, several of these were never regular public drops: 18.10.1 shipped security fixes as a private release, and 18.10.7 (08/19/26) is described as "a public equivalent of 18.10.6 that announces security issues addressed in the private release 18.10.1". So 18.10.7 is specifically the publication vehicle for those fixes rather than an ordinary patch. Whether GitHub Release entries for these tags get created retroactively is a maintainer decision; I have not found any statement about it. Note the break is recent: the June patch trains (v18.9.1, v18.9.2, v17.7.23 through v17.7.26) all have normal Release entries, so the gap starts with the 18.10 train in July.

2. For monitoring, the tag feed already carries everything the Releases page is missing: https://github.com/gravitational/teleport/tags.atom currently lists v18.11.0, v18.10.7 and v17.7.28. The releases.atom feed also includes those entries right now, but tags.atom tracks git refs, which exist for every one of these versions, so it should keep working regardless of whether Release objects are ever published.

References:

• https://goteleport.com/docs/changelog/
• https://github.com/gravitational/teleport/tags.atom
• https://github.com/gravitational/teleport/releases.atom

Checked against the live REST and git-tag APIs and the docs changelog today (2026-08-25); I did not ask the maintainers why the Releases page stopped updating.

[uedvt359]

checking tags.atom is not a great solution, since it cannot include changelogs and also contains a bunch of tags that don't correspond to proper releases, unfortunately.

[uedvt359]

@r0mant : as the person who seems to be in charge of releases, may i please ask for your input on this? this also affects the built-in update mechanism:

teleport/lib/versioncontrol/github/github.go

Line 109 in 1283425

res, err := clt.Get(fmt.Sprintf("https://api.github.com/repos/gravitational/teleport/releases?page=%d&per_page=%d", n, size))