docs(constraints): document the possible `constraints` and `installTools` by jamietanna · Pull Request #42837 · renovatebot/renovate · GitHub
Skip to content

docs(constraints): document the possible constraints and installTools#42837

Draft
jamietanna wants to merge 3 commits intomainfrom
docs/constraints-docs
Draft

docs(constraints): document the possible constraints and installTools#42837
jamietanna wants to merge 3 commits intomainfrom
docs/constraints-docs

Conversation

@jamietanna
Copy link
Copy Markdown
Contributor

Changes

Context

Please select one of the following:

AI assistance disclosure

Did you use AI tools to create any part of this pull request?

Please select one option and, if yes, briefly describe how AI was used (e.g., code, tests, docs) and which tool(s) you used.

  • No — I did not use AI for this contribution.
  • Yes — minimal assistance (e.g., IDE autocomplete, small code completions, grammar fixes).
  • Yes — substantive assistance (AI-generated non‑trivial portions of code, tests, or documentation).
  • Yes — other (please describe):

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests, but ran on a real repository, or
  • Both unit tests + ran on a real repository

The public repository:

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.
This requires `toolNames` and `additionalConstraintNames` are exported
for use.
…ols`

Now we have a stronger type for what a valid tool constraint is, and
what additional constraints are, we should be very explicit with what
each option is, and specify them in the `constraints` as well as our
`installTools` docs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: what are the valid constraints and installTools options?

1 participant