Currently the the order of security scheme providers constants is not deterministic (e.g. as in the generated code snippet below). This is because the order is determined by iterating over a map, which is deliberately randomized in Go.

const (
	TokenAuthScopes = "TokenAuth.Scopes"
	BasicAuthScopes = "BasicAuth.Scopes"
	JWTAuthScopes   = "JWTAuth.Scopes"
)

We currently check for changes to the generated files to determine whether additional steps are needed in our CI workflow. This non-deterministic behaviour is causing frequent false positives in our api change detection, which unnecessarily interrupts our CI workflow.

I've created a fix for this issue.