Version 0.9

Release Notes for v0.9.6 – Bug Fix Release

Release Date: 08/28/2026

BugFixes (v0.9.6)

  • #611 Rolling back docker secure image, not available on all platforms.
  • #607 Added Folder listing pagination.
  • #609 Dashboard v2 listing dropped most dashboards in any org with more than one page of results.
  • #604 Token (service account) auth resolved its organization via the legacy /api/user/orgs endpoint, which tokens cannot use, and silently fell back to the default org with no error.
  • Anonymous access hit a hard “namespace mismatch” error from the App Platform because it was routed through the same broken token org-lookup.

TechDebt (v0.9.6)

  • #605 Docker base image switched from alpine:latest to cgr.dev/chainguard/wolfi-base:latest.
  • Added a multi-org Grafana integration test suite (multi_org_auth_integration_test.go) covering service-account token and anonymous access pinned to a non-default org, plus regression tests for both pagination fixes above.

Release Notes for v0.9.4

Release Date: 08/27/2026

  • Grafana 11+ / 12+ (v1 legacy API — default behavior, no config changes required)
  • Grafana 13+ (v2 App Platform API — auto-enabled, no config changes required)

Breaking Changes (v0.9.4)

Note

This release has a major TUI revamp that should capture all configuration options as of 0.9.3. This should allow the user to configure GDG using the easy-to-use wizard as well as providing a custom configuration file if that’s preferred.

Dashboard File Format Change

Dashboards downloaded from a Grafana v13+ instance are saved in a new format. These files are not compatible with older versions of GDG. If you need to roll back, re-download your dashboards after downgrading.

Dashboard Filter Flag: –dashboard Replaced by –uid

The --dashboard / -d flag has been renamed to --uid / -u and now filters by dashboard UID instead of slug. If you previously used --dashboard bandwidth-dashboard, update your scripts to use --uid 000000003 (the UID shown in gdg backup dash list). The dashboard listing output now also shows the Grafana UID (resource name) instead of the Kubernetes metadata UID.

  • Dashboard files downloaded from Grafana v13+ use a new storage format. Files from older GDG versions will continue to upload correctly, but re-downloading is recommended to migrate to the new format.
  • The --dashboard / -d flag is replaced by --uid / -u. Filtering now matches the dashboard UID visible in gdg backup dash list output rather than a slug derived from the title.

Changes (v0.9.4)

  • #601 The --dashboard / -d filter flag has been renamed to --uid / -u and now filters by dashboard UID instead of slug, since Grafana no longer exposes slug data reliably in the search API response. The gdg backup dash list output now shows the Grafana UID (resource name) in the UID column, which can be passed directly to --uid.
  • 569 Added plugin rekey — updates all stored values with their encrypted equivalent when enabling a new cipher plugin, so existing backups stay accessible.
  • 568 A plugin registry was added to help discover available plugins.
  • 566 TUI support for the plugin registry, allowing plugin discovery and selection from the interactive wizard.
  • #590 GDG now auto-detects Grafana v13+ and switches to the App Platform dashboard API with no configuration changes required. Dashboards are saved in a new Kubernetes-style format carrying additional metadata (folder, resource name, API version); v12 and older continue using the legacy API and flat JSON format unchanged. Repositories containing a mix of old and new format files are handled correctly, with a warning logged for any file that cannot be applied to the connected server.
  • #525 / #598 Added filtering support for alerting contact points. Filters are configured under alert_settings.contact_points.filters and apply to all contact point operations (list, download, upload, clear).
  • #598 Added --filter flag to all gdg backup alerting templates subcommands for name-based regex filtering.
  • #598 The interactive config wizard (gdg tools ctx add) now includes an Alert Settings phase for configuring contact point filters.

TechDebt (v0.9.4)

  • 570 Upgraded website code to a latest version.
  • 571 Fixed documentation issues that help clarify how to use gdg for new users
  • 574 Upgraded to use huh v2 (and later replacet with bubbles deprecating huh from code base)

Release Notes for v0.9.3

Release Date: 03/05/2026

Breaking Changes (v0.9.3)

  • Dropped gdg tools devel completion since it’s already exposed as a top level command gdg completion

BugFixes (v0.9.3)

  • #543 Env vars not working due to a conflict with the secure_location pattern that was previously introduced. Env will work if secure location not used. Next major release (0.10.x) will fix this to allow for Env to take precedence over any config values.

Changes (v0.9.3)

  • #565 Dropping S3 TUI and merging logic into context builder
  • #564 Adding TUI config generator updates.
  • #563 Adding TUI for S3 configuration
  • #557 Adding support for patching folder UID when missing and folder auto-creation.
  • #557 Adds label and folder based filtering to alert rules.
  • #559 Adds name UID based filtering to alert rules.

TechDebt (v0.9.3)

  • Bug #501 Fixing issues with test failures due to containers not being available.
  • #539 Added test to cover to plugin code path.
  • #488 Added an Env to disable enterprise tests. Allow contributors to not be blocked without a license.
  • #531 Fixing documentation issues with the Getting Started guide and css/icons rendering behavior.
  • General dependency and tooling update, upgrade to go 1.26.0, npm updates
  • #558 Refactors code base to follow port/adapters/domains

Release Notes for v0.9.2

This is a quick bug fix release to address the behavior of alert rules. The other changes are enabling encryption for connection settings as well. This should cover all sensitive data that GDG manages.

Changes (v0.9.2)

  • Bug: #535 Fixing behavior with context override
  • Bug: #537 Fixing issues with Alert Rules filtering and folder Crud.
  • Feature: #538 Adding encryption support to connections secure data.
  • chore: #530 Fixing video demo and context deletion logic

Release Notes for v0.9.1

Release Date: 01/08/2026

  • Grafana 11+

Release Notes (v0.9.1)

This was a pretty big change with it has a good bit of breaking changes. The idea of the secure folder was added a while ago that allowed for separation of sensitive data out of the main config. This released has removed all sensitive data from the main config. That includes passwords, tokens, cloud keys etc.

for k8s and docker setup this change enable secrets to be mounted from your secret manager and it allows a clear separation between secrets and config.

Plugin System:

State: Beta (might still have some breaking changes in future releases)

extism plugin system was incorporated into gdg. The plugin system is disabled by default. There is a performance hit when using them, so if you don’t need them it’s better to keep the feature off. The main reason this was added was because sensitive data is pulled in with the alerting contact points. If you use that feature and store your backups in git it’s highly encouraged to use a cipher plugin.

There are two working currently available at: gdg-plugins

  1. ansible vault cipher
  2. aes-256-gcm

You can also easily write your own. The cipher plugin takes in a string and returns a string. It’s likely one of the simplest ones that will be supported.

More detailed docs will be available with the official docs.

Caution

Not all data in the secure folder currently supports encryption. Datasource auth is still in plaintext. The next release should address this. issued #524, will address this change.

Breaking Changes (v0.9.1)

  • #502 Password and Tokens in config file has been deprecated.
  • #510 Renamed default config to gdg.(yaml|yml). importer.yml will still work but a warning will be printed. importer.yml will be dropped in 0.10.x
  • #513 Changed location of S3 secure auth.
    • Additionally:
      • custom: true flag has been removed. It was deprecated 0.8.x. Please use cloud_type: custom instead.
      • Behavioral change. AWS_ACCESS_KEY and AWS_SECRET_KEY will now override config values. This is now consistent with how the rest of the GDG config handled env overrides.
  • #504 Changing behavior of alert rules. Since they are tied to a given folder, the rules will be saved in the given folder. Additionally, folder filtering has been added to allow a user to only include rules they are interested in.

Changes (v0.9.1)

  • #520 Adding plugin support.
  • #515 Add support for Alerting Timings
  • #519 Add support for library elements pagination (more than 100 elements)

Bug/Security Fixes (v0.9.1)

  • #521 pnpm security update JS

Tech Updates (v0.9.1)

  • #497 Refactoring of buildConfigSeachPath
  • #503 Ensuring only one CI job run for a PR
  • #509 Switching to use OpenAPI endpoint for HeathEndpoint
  • #512 Changing naming convention to auth_context

Contributors (v0.9.1)

Release Notes for v0.9.0

CICD Build failures, skipping versions. Skipping to next version.