hasura/graphql-engine · error
config %v is not supported
Error message
config %v is not supported
What it means
NewProjectMetadata refuses to construct a ProjectMetadata when the project's config version is <= cli.V1 (i.e. config version 1). Hasura CLI v2+ metadata operations only support config version 2 and 3; version-1 projects must be migrated. The message interpolates the actual version value found in config.yaml.
Source
Thrown at cli/pkg/metadata/project_metadata.go:140
ec.Stderr = io.Discard
err := ec.Prepare()
if err != nil {
return nil, errors.E(op, err)
}
p := &ProjectMetadata{ec}
for _, opt := range opts {
opt(p)
}
err = ec.Validate()
if err != nil {
return nil, errors.E(op, err)
}
if ec.Config.Version <= cli.V1 {
return nil, errors.E(op, fmt.Errorf("config %v is not supported", ec.Config.Version))
}
return p, nil
}
View on GitHub (pinned to 724551b9ae)
Solutions
- Update config.yaml to `version: 3` (preferred) or `version: 2` and adjust config keys to the new format
- Or use the legacy Hasura CLI v1 binary for that project
- Run `hasura init` in a fresh directory with the new CLI and port over migrations/metadata to get a valid v3 config
- Ensure the correct project directory is being used (the one with the upgraded config.yaml)
Example fix
# before (config.yaml) version: 1 # after version: 3
Defensive patterns
Strategy: validation
Validate before calling
cfg, _ := util.ParseConfig("config.yaml")
if cfg.Version <= 1 {
return fmt.Errorf("upgrade config.yaml to version 2 or 3 before using metadata commands")
} Prevention
- Upgrade project config.yaml as part of CLI upgrades
- Check config version in CI before running any hasura commands
- Document the supported config versions for your team
When it happens
Trigger: Calling NewProjectMetadata in a project whose config.yaml has `version: 1` (or a value parsing as <= V1, e.g. 0 or missing). The check runs after ec.Validate(), so the config itself is otherwise valid.
Common situations: Opening a legacy Hasura v1 project with a modern CLI; config.yaml left at version 1 after a partial upgrade; CI checking out an old branch with a v1 config; version field typo like `version: 1.0`.
Related errors
- config %v is not supported
- error in writing config: %w
- cannot validate new config: %w
- pulling latest actions codegen files from internet failed: %
- unable to fetch introspection schema: %w
AI-assisted analysis of hasura/graphql-engine@724551b9ae (2026-08-28).
Data as JSON: /api/errors/9cd25109b94c4c6b.
Report an issue: GitHub.