[jenpaff]

tempo/v1.17.0, the required T13 release, was published on October 26, 2026. Replace the "coming soon" preview on the releases page and the T13 page with links to the release, add its date, and note that tag watchers need tempoup 0.0.18 or later.

Validation: pnpm check passes.

Prompted by: @jenpaff

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
tempo-docs	Ready	Preview	Oct 26, 2026 8:45pm UTC

[claude]

LGTM. This is a small docs update that marks tempo/v1.17.0 as released.

What was reviewed:

• The release-table row and the T13 Release row in network-upgrades.mdx, plus the T13 status box in t13.mdx. The link and date formatting match the other rows (linked tag, "Mon DD, YYYY").
• The release URL with the slashed tag (releases/tag/tempo/v1.17.0). It follows the new tempo/vX.Y.Z tag format the row describes.
• The rest of the docs for any other "coming soon" or unlinked v1.17.0 references. None remain; the only other "coming soon" is about validator data resets and is unrelated.
• The Oct 26 release date is before the October 29 testnet and November 3 mainnet activation dates.

Extended reasoning...

Docs-only change to two MDX pages: it replaces the "coming soon" text for the T13 node release with links to its GitHub release, adds the release date, and adds a note about the tempoup version. It touches no code and nothing security-sensitive. No CODEOWNERS or ANTOWNERS files cover these paths, and the timeline shows no other reviewers or open objections. The bug hunt stopped because it ran dry (dry_streak) and reported no findings. The tempoup 0.0.18 minimum version comes from the author and can't be checked from this repo; it's a reasonable claim to accept for a docs note.