[sanderson]

What changed

reference/release-notes.md gains a v1.2.0 entry dated 2026-10-27 and takes over the download link. "Before you upgrade" covers the audit signing key (Important callout) and the new audit:read permission, the rename of duplicate configuration and group names, API token access changes, and an "API changes" list (moved heartbeat data endpoints, the status check route, session-only routes, token-scoped token management, the password-reset code removal, threshold validation). Features cover security advisories, pre-shared and bootstrap tokens, audit signing and verification, the Agents page and agent detail redesigns, the heartbeat service health indicator, the default heartbeat template with logs, the Telegraf-Agent-IP header, the multi-architecture Docker image, signed digests, and the Google Cloud secret store plugin. Fifteen bug fixes follow.

Why

Telegraf Controller 1.2.0 ships without a release-notes entry. Items were collected from every telegraf_ui pull request in development since v1.1.2 and verified against the source; changes already released in v1.1.1 and v1.1.2 are omitted.

Impact:

One page. The download link moves from v1.1.2 to v1.2.0. products.yml and tc_downloads.yml are left for the release step.

Verification:

Vale (warning level): 0 errors; one pre-existing warning on the v0.0.1-alpha heading. yarn lint-codeblocks: no failures. Rendered with hugo server; every heading and all 19 links in the new entry resolve, including fragments.

Checklist

• Rebased/mergeable
• Local build passes (npx hugo --quiet)

[github-actions]

Vale Style Check Results

Metric	Count
Errors	0
Warnings	1

Warnings (1)

File	Line	Rule	Message
content/telegraf/controller/reference/release-notes.md	783	InfluxDataDocs.Capitalization	'v0.0.1-alpha {date="2026-01-01"}' should be in sentence case

---

✅ Check passed

[github-actions]

Release version check

Product	Release notes	data/products.yml	Status
telegraf_controller (latest_patch)	1.2.0	1.2.0	✅ in sync

💡 Badge new features with the version

Documenting a new feature? Add a version badge in the page frontmatter — the
same mechanism used elsewhere in the docs:

• metadata: [InfluxDB 3 Core v3.11+] — badge list under the page title
• updated_in: v3.11 — an "Updated in v3.11" badge
• introduced: v3.11 — a "‹Product› v3.11+" badge
• menu.params.state: new — a "NEW" pill on the sidebar nav item

For inline version text, use {{< latest-patch >}} / {{< current-version >}},
which read the value from data/products.yml so it stays correct automatically.

[github-actions]

🔗 Link Check Results — Link Check Bot

❌ 1 broken link(s) found — fix them before merging.

Metric	Value
Files Checked	1
Total Links	213
Errors	1
Warnings	1
Success Rate	98.12206%

Broken Links

Source File	Broken URL	Error	Report
content/telegraf/controller/reference/release-notes/_index.md	https://www.influxdata.com/blog/telegraf-controller-1-2/	Rejected status code: 404 Not Found	Report

⚠️ 1 warning(s) (do not fail CI)

Source File	URL	Issue
content/telegraf/controller/reference/release-notes/_index.md	https://support.influxdata.com/	Network error: SSL certificate not trusted. Use --insecure if site is trusted (e…

---

_{Full details: workflow run summary and artifact. Last updated: 2026-10-26 20:20:44 UTC}