hasura/graphql-engine · error

config %v is not supported

Error message

config %v is not supported

What it means

NewProjectDeploy refuses to deploy projects whose config version is v1 (or lower): only config v2/v3 projects are supported by project deploy. The check `ec.Config.Version <= cli.V1` throws 'config %v is not supported' after the ExecutionContext validates cleanly.

Source

Thrown at cli/pkg/deploy/project_deploy.go:85

	ec.Stderr = io.Discard

	err := ec.Prepare()
	if err != nil {
		return nil, errors.E(op, err)
	}

	d := &ProjectDeploy{ec}
	for _, opt := range opts {
		opt(d)
	}

	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 d, nil
}

View on GitHub (pinned to 724551b9ae)

Solutions

  1. Upgrade the project config: run the config migration (e.g. `hasura scripts update-project-v2` flow or the v3 updater) to move to version 2/3
  2. Manually set `version: 3` in config.yaml and fix any incompatible keys per migration docs
  3. Make sure you're running deploy from the actual project root with the current config

Example fix

# before (config.yaml)
version: 1

# after
version: 3
Defensive patterns

Strategy: validation

Validate before calling

if ec.Config.Version <= 1 {
    return fmt.Errorf("upgrade config.yaml to version 2/3 before deploy")
}

Try / catch

d, err := deploy.NewProjectDeploy(ec, ...)
if err != nil && strings.Contains(err.Error(), "not supported") {
    // migrate config to v2/v3, then retry
}

Prevention

When it happens

Trigger: Running `hasura deploy` (project deploy) in a directory whose config.yaml still says `version: 1`; hit immediately at construction of the deploy command.

Common situations: Very old Hasura projects never migrated off config v1; a config.yaml accidentally edited back to version 1; running deploy in the wrong directory containing a stale config.

Related errors


AI-assisted analysis of hasura/graphql-engine@724551b9ae (2026-08-28). Data as JSON: /api/errors/85bcba7dc8fa46bb. Report an issue: GitHub.