Changelog
1.7.2
This release contains only dependency changes.
- Decrease required Go version to 1.27.2 so that Grafana's internal validator can function
1.7.1
This release contains only dependency updates.
- Technical: upgrade Grafana packages to 13.1.8 and plugin-ui to 0.17.8 while retaining React 18
- Technical: upgrade plugin signing and E2E tools, use Node.js 24 LTS, and remove unnecessary dependency overrides
- Security: upgrade the Go toolchain to 1.27.3 and update Go dependencies to address reported vulnerabilities
- Security: update markdown-it to 15.0.3 to fix CVE-2026-111758
- Security: update DOMPurify, Immutable, js-cookie, Moment, and UUID and remove vulnerable signing-tool dependencies
1.7.0
- Fix: #28 fixed GraphiQL query editor visibility when editing an alert rule
- Feature: #20 update to GraphiQL version
- Feature: resizable GraphiQL editor
- Feature: added "expand editor" button allowing an almost full screen GraphiQL editing experience
- Data source configuration changes relating to Migrating from DataSourceHttpSettings component
- Technical: many dependency updates (as always)
1.6.1
Continued updates for Grafana 13 / React 19. No real changes since 1.6.0 other than fixing plugin signing.
1.6.0
Updates to support Grafana 13. Upgraded GraphiQL dependency.
1.5.1
Fixed regression within the query editor that occurred when constant labels were used. Dependency updates for stability.
1.5.0
- Feature: #14 support for variable queries
- The data path can now point to a primitive, or an array of primitives. This is most useful for variable queries, but can also be used in other queries.
- Feature: Frame exclusion - the option to configure labels to be excluded from the data frame. Especially useful if you are using numeric values for labels.
- Beta feature: when exploding an array of primitives, you may refer to the index by using the
#indexsuffix only within labels that reference fields.
1.4.1
Some small fixes.
- Handle against empty query object. This guards against a bug that occurs when a new panel is created, the query is sometimes empty, rather than the default query.
- Correctly handle case when the
datafield of the GraphQL response is null - Better error handling in the backend.
1.4.0
The big feature in this release is exploded array paths, which allows nested arrays within responses to be "exploded" into multiple rows.
- Feature: #6 support for exploded array paths which allow nested arrays to be turned into multiple rows instead of multiple columns
- Fixed: #15 data paths can now index into arrays.
1.3.1
Fixed #9 which was a bug where arrays used inside the variables section would incorrectly get turned into an object before being passed to the backend. Additionally, there are many internal dependency upgrades to fix a security vulnerability that prevented 1.3.0 from officially being released.
1.3.0
Merged #8 which passes a request's HTTP headers to the GraphQL server. This change should respect the checkboxes under the "Auth" section of the data source's configuration so that OAuth and cookie headers are only sent if you toggle their setting.
Additionally, these headers are now always passed to the GraphQL server for most queries:
X-Datasource-UidX-Grafana-Org-IdX-Panel-IdX-Dashboard-Uid
1.2.1
Updated LICENSE link in README.
1.2.0
Merged #5
which updates the internal libraries for better HTTP header support that can be configured within the data source itself.
Additionally, all GraphQL requests will include a Accept: application/json header in every request.
This additional header matches the GraphQL over HTTP spec for better compatibility with GraphQL servers.
1.1.1
No new features or fixes.
Stability
- First release that is officially signed
1.1.0
New Features
- Added "Advanced Variables JSON" to define a variables JSON object that has interpolation performed on the JSON string itself, rather than strings within the JSON
- This is added functionality and is not meant to replace or change the existing functionality. Using the variables configuration from the GraphiQL editor and advanced variables JSON at the same time is supported.
Stability
- Resources are properly closed
- Panics are no longer used and better logging is done in the backend
- Unnecessary
console.log()calls moved to existingconsole.error()calls
1.0.1
Fixes
- Numeric values are now exported as
float64values, which allows alerting queries to work correctly - An undefined variables object used to cause an error to be logged. Null/undefined
variablesfield defined via provisioned queries now cause no error message to be logged.
1.0.0
Initial release.