v1.6.11
1.6.11 (2026-08-17)
Chores
- the release pipeline now produces a build-provenance attestation the catalog recognizes (#305): the 1.6.10 submission came back with
no-provenance-attestation— "this plugin was built without build verification" — even though the workflow already ranactions/attest-build-provenance. The validator checks for an attestation in the specific shape Grafana's own tooling emits, so a hand-rolled step does not count no matter how correct the SLSA statement is. Building throughgrafana/plugin-actions/build-pluginproduces it in the expected form. Tests, theverify-dist.jspackaging check and the community-signature assertion all still gate the release —build-pluginruns none of them itself, so they now sit in atestjob the release job depends on, and the packaged zip is still rejected if it carries no communityMANIFEST.txt. Two consequences worth knowing: the checksum published alongside the zip is now SHA1 rather than MD5, and the GitHub release is created as a draft to be published after review - exporter Go toolchain raised to 1.26.6 (#298): the catalog's
govulnchecksource scan reported three reachable stdlib advisories — GO-2026-5972 / CVE-2026-33818 (encoding/asn1recursion depth), GO-2026-6089 / CVE-2026-56853 (net/httpnot applyingReadHeaderTimeoutto the unencrypted HTTP/2 check) and GO-2026-6090 / CVE-2026-56862 (crypto/tlspost-handshake message limits), all fixed in 1.25.13 and 1.26.6. Thegodirective moves only to 1.25.13, the patched release on the line it was already on, rather than to 1.26.6: the validator's runner usesGOTOOLCHAIN=local, and a directive above its own version turns the scan from a warning into a hard failure, which is exactly what happened when this was last set to 1.26.5. Thetoolchaindirective carries the 1.26.6 recommendation. None of this reaches a Grafana instance — the module is the simulated-WAN Prometheus exporter behind the demo dashboards and is not part of the panel
This Github draft release has been created for your plugin.
Note: if this is the first release for your plugin please consult the distributing-your-plugin section of the README
If you would like to submit this release to Grafana please consider the following steps:
- Check the Validate plugin step in the release workflow for any warnings that need attention
- Edit this draft release, adjust these notes accordingly and click Publish Release
- Navigate to https://grafana.com/auth/sign-in/ to sign into your account
- Once logged in click My Plugins in the admin navigation
- Click the Submit Plugin button
- Fill in the Plugin Submission form:
- Paste this .zip asset link in the Plugin URL field
- Paste this .zip.sha1 link in the SHA1 field
If the links above are not working, you must first edit this draft release and publish it.
This build has been attested. You can view the attestation details here
What's Changed
- chore: remove the stale AppVeyor config by @allamiro in #353
- ci(release): recognized build-provenance via grafana/plugin-actions by @allamiro in #305
- release: v1.6.11 — recognized provenance attestation + patched Go toolchain by @allamiro in #356
Full Changelog: v1.6.10...v1.6.11