feat: gdg upgrade to work with Grafana 13 edited dashboards

[HelenaLvH]

Is your feature request related to a problem? Please describe.

Upgraded to Grafana 13.1 0 using gdg 0.9.3 and I cannot import dashboards touched by Grafana 13 using gdg.
Flow:
Export using gdg from dev host=>git
git=> prod host
Import using gdg

This gives me tag a tag error for all dashboards edited by Grafana 13

Id":3461768331415552,"folderId":0,"folderUid":"fdrbeg3pdczk0a","description":"","path":"","removed":false}
2026-07-09 09:19:23 WRN v2/filters.go:96 unable to read obj value err="no valid title found" filter=TagsFilter
2026-07-09 09:19:23 WRN api/dashboards.go:536 validation failed, skipping file=/data/appv/svc/grafana/cicd-vfmu-grafana-provisioning-components/gdg/org_isc-sps-vfmu/dashboards/VFMU/vfmu-incident-management.json err="dashboard fails to pass tag filter: tagFilter: []"

Describe alternatives you've considered

As a workaround I run a script to add the missing tag before I run the gdg import

#!/bin/bash
# tag_change_all.sh - add missing "tags": [] to all dashboard JSONs and list changed files

BASE=/data/appv/svc/grafana/xx/gdg/org_isc-xx/dashboards

changed=0
checked=0

echo "Scanning: $BASE"
echo "--- changed files ---"

while IFS= read -r -d '' file; do
    checked=$((checked+1))
    if [ "$(jq 'has("tags")' "$file")" = "false" ]; then
        if jq '. + {tags: []}' "$file" > "$file.tmp" && mv "$file.tmp" "$file"; then
            echo "${file#$BASE/}"
            changed=$((changed+1))
        else
            echo "ERROR: failed to update $file" >&2
            rm -f "$file.tmp"
        fi
    fi
done < <(find "$BASE" -name '*.json' -print0)

echo "---------------------"
echo "Checked: $checked files, changed: $changed"

Additional context
Related to (#422)

[safaci2000]

That new Dashboards created with V13 and possible V12 (I think it was feature gated) is a completely different API. It's bit in the TODO list but I need to read up a bit more on the API changes and redesigns.

[HelenaLvH]

I can understand the complexity. Currently we have a workaround for the one problem we encountered but it would be great if we could continue to use gdg since we really like what you have built.

[safaci2000]

Okay, so I can add a work around for the missing tags. My filter logic was a bit too aggressive, that should not have errored out in the first place. (I just pushed a small MR for that. )

The issues right now is that there is no official client that was released. The current client they have is based on: /public/api-merged.json which only captures the /api/ endpoint. The new APIs are all under apis, like: apis/dashboard.grafana.app/v2/

I think I have a working pattern now. I'll need to spend some time debugging this but since grafana cut an official GA release, we can add this in now.

This will likely be a blocker for us as well. All the tooling across the ecosystem will need to be updated if they kill the legacy API.

[safaci2000]

This fixes the workaround you had to add in: #590, I'm working on the new API, but still need to think through how to migrate to the new version without causing backward compatibility issues. The API, format, everything has changed at this point.