Should we introduce secfixes field in the build.Configuration?

[Dentrax]

Since wolfi packages started to use secfixes field in the package configs, build.Configuration struct does not include the secfixes field yet. I'm curious about the rationale of introducing this field. My use case of this to make strict validation while parsing Melange config file into build.Configuration{} for linting whether given config is valid using yamlv3 Go package. (for $ wolfictl lint command)

Alternative workaround is creating a new struct that inherit Melange configuration, which I would not to prefer in the first place:

type Configuration struct {
  build.Configuration
  secfixes []string
}