Files
renovate/lib/util/exec
Jamie Tanna 53dcdba84d fix(validation): validate constraints (#42825)
* fix(validation): validate `constraints`

To provide better coverage for our users of what is a valid option for a
`constraints` value, we can validate the overall format of the
`constraints` block, as well as the given names of constraints.

Where we have a Tool defined, we can use the default versioning for that
Tool to validate the constraint's value.

For now, both the validation of the `constraints`' value, and the
validation of `constraints`' names will be a warning, but in the future
may be made an error.

* chore(validation): remove check for `compatibility`

As this was renamed in #7308. It's been long enough since then that we
can remove this check.

* chore(validation): add logger in `else` case

For coverage fix, and also to provide insight when this does happen

* fixup! chore(validation): add logger in `else` case

* fixup! chore(validation): add logger in `else` case

* key

* coverage

* Remove duplicate function

As it's been pulled in via another PR.

* fixup! docs(constraints): document the possible `constraints` and `installTools` (#42837)

As it can't be `undefined`.

* test: coverage

And more whitespace to make it clearer they're two separate `if` blocks.

* typo

* typo

---------

Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
2026-04-28 10:21:41 +00:00
..
…
…
…
2026-04-01 07:46:34 +00:00
…