Consider pinning Vale more tightly, to avoid unplanned rule changes

[dwilding]

Here's how we currently pin Value in Sphinx Stack requirements:

sphinx-stack/docs/requirements.txt

Line 34 in d701c98

vale~=3.13

This allows projects to use the latest 3.x version of Vale. Version 3.17 introduced support for inline scopes, which means that previously-unchecked text (e.g., link text) is now checked by the spelling check.

Since Vale releases can cause unexpected changes for users of Sphinx Stack, I wonder whether we should pin the version more tightly. Either pin to a minor version or exact version.

What do you think @jahn-junior?

[jahn-junior]

No objections to pinning to a minor version. I hadn't considered that new failure points aren't really "breaking" from Vale's perspective.